From: Juri Lelli <juri.lelli@gmail.com>
To: Tim Blechmann <tim@klingt.org>
Cc: Daniel Bristot de Oliveira <daniel@bristot.me>,
linux-rt-users@vger.kernel.org
Subject: Re: SCHED_DEADLINE as user
Date: Fri, 17 Aug 2018 12:28:10 +0200 [thread overview]
Message-ID: <20180817102810.GC27071@localhost.localdomain> (raw)
In-Reply-To: <c2b1a7a4-db8c-b8bd-6623-5c66b55ee6d2@klingt.org>
On 17/08/18 18:08, Tim Blechmann wrote:
> hi juri,
>
> >>> i wonder, what's the preferred way to obtain SCHED_DEADLINE privileges
> >>> as non-root user?
> >>
> >> Hi Tim,
> >>
> >> It is still not possible to use sched deadline as a non-root user :-(.
> >
> > Indeed, but Tim, is this hindering you from experimenting/using
> > DEADLINE?
>
> it's a showstopper for using it in audio applications, which are running
> as user.
> audio applications typically use SCHED_FIFO. however they are
> rate-monotonic by design, so i wanted to evaluate how SCHED_DEADLINE
> behaves here.
Right. Exactly what I started to think about lately as well.
>
> > Asking because we might want to have a look at how to relax the current
> > privileges requirement.
>
> please :)
Anything to try attracting new users. :-P
More seriously, could you please describe in a bit more details your
specific use case? Based on JACK I guess? Is it the application you are
interested into public available somewhere?
Thanks,
- Juri
next prev parent reply other threads:[~2018-08-17 13:31 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 [this message]
[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
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=20180817102810.GC27071@localhost.localdomain \
--to=juri.lelli@gmail.com \
--cc=daniel@bristot.me \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim@klingt.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).