From: luca abeni <luca.abeni@santannapisa.it>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: Tim Blechmann <tim@klingt.org>,
Daniel Bristot de Oliveira <daniel@bristot.me>,
linux-rt-users@vger.kernel.org,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
Subject: Re: SCHED_DEADLINE as user
Date: Thu, 23 Aug 2018 15:00:40 +0200 [thread overview]
Message-ID: <20180823150040.7da1624f@luca64> (raw)
In-Reply-To: <20180823123739.GC31443@localhost.localdomain>
On Thu, 23 Aug 2018 14:37:39 +0200
Juri Lelli <juri.lelli@gmail.com> wrote:
[...]
> > > Maybe the existing system wide sched_rt_{period,
> > > runtime}_us are enough?
> >
> > I do not know... A cgroup-based interface looks more powerful (and
> > not so difficult to implement... :), and would allow the sysadmin
> > to decide which users can use SCHED_DEADLINE, how much
> > SCHED_DEADLINE bandwidth can each user/group use, etc...
>
> How about extending PAM limits instead? It looks like it's what (e.g.)
> audio users rely on already [1]. It is maybe possible to add
> dlruntime, dlperiod, dldeadline parameters in there?
Ok, I do not know much about these PAM limits... Where can I find more
information? What do we need to implement exactly, to add these
dlruntime, dlperiod, dldeadline parameters?
Thanks,
Luca
next prev parent reply other threads:[~2018-08-23 16:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 6:08 SCHED_DEADLINE as user Tim Blechmann
2018-08-15 8:21 ` Daniel Bristot de Oliveira
2018-08-17 9:51 ` Juri Lelli
2018-08-17 10:08 ` Tim Blechmann
2018-08-17 10:28 ` Juri Lelli
[not found] ` <513fd544-bc51-7ea6-8b94-983d28922a66@klingt.org>
2018-08-20 8:54 ` Juri Lelli
2018-08-20 11:54 ` Tim Blechmann
2018-08-20 12:38 ` Daniel Bristot de Oliveira
2018-08-20 13:55 ` Tim Blechmann
[not found] ` <e207a65d-b1af-3fb1-8802-d1c05c0a9118@bristot.me>
[not found] ` <05fbd5a4-f354-e084-cf40-8488548d7cb1@klingt.org>
2018-08-21 6:55 ` Tommaso Cucinotta
2018-08-21 7:38 ` Juri Lelli
2018-08-22 8:49 ` Juri Lelli
2018-08-21 7:17 ` Tommaso Cucinotta
2018-08-21 7:59 ` Tim Blechmann
2018-08-23 9:56 ` luca abeni
2018-08-23 10:23 ` Juri Lelli
2018-08-23 10:43 ` luca abeni
2018-08-23 12:37 ` Juri Lelli
2018-08-23 12:58 ` luca abeni
2018-08-23 13:00 ` luca abeni [this message]
2018-08-23 13:09 ` Juri Lelli
2018-08-23 13:30 ` luca abeni
2018-08-23 13:45 ` Gene Heskett
2018-08-23 16:01 ` Chris Friesen
2018-08-23 18:07 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180823150040.7da1624f@luca64 \
--to=luca.abeni@santannapisa.it \
--cc=daniel@bristot.me \
--cc=juri.lelli@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim@klingt.org \
--cc=tommaso.cucinotta@santannapisa.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.