public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Matt Mackall <mpm@selenic.com>
Cc: Chris Wright <chrisw@osdl.org>,
	"Jack O'Quin" <jack.oquin@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org,
	Paul Davis <paul@linuxaudiosystems.com>,
	Con Kolivas <kernel@kolivas.org>,
	rlrevell@joe-job.com
Subject: Re: 2.6.11-rc3-mm2
Date: Fri, 11 Feb 2005 18:49:05 +0100	[thread overview]
Message-ID: <20050211174905.GC17387@elte.hu> (raw)
In-Reply-To: <20050211173751.GK15058@waste.org>


* Matt Mackall <mpm@selenic.com> wrote:

> > > Yes. There's also the whole soft limit thing.
> > 
> > i'm curious, how does this 'per-app' rlimit thing work? If a user has
> > jackd installed and runs it from X unprivileged, how does it get the
> > elevated rlimit?
> 
> It needs a setuid launcher. It would be nice to be able to elevate the
> rlimits of running processes but the API doesn't exist yet.

With a setuid launcher you need _zero_ kernel help to get SCHED_FIFO: if
you have a launcher then already today it can just give SCHED_FIFO to
jackd and be done with it!

	Ingo

  reply	other threads:[~2005-02-11 17:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 20:51 2.6.11-rc3-mm2 Jack O'Quin
2005-02-11  0:04 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  0:47   ` 2.6.11-rc3-mm2 Chris Wright
2005-02-11  2:09     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  2:22       ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  3:26         ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  3:41           ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11  5:04             ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  6:34               ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  6:42                 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  5:09             ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  6:57             ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  7:54               ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:25                 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  8:48                   ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:58                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  9:01                       ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:04                   ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:27                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49                   ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 19:42                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 19:57                       ` 2.6.11-rc3-mm2 Lee Revell
2005-02-11  8:14       ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:22         ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-11  8:41         ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  8:59           ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:40             ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  9:53               ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:37                 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49                   ` Ingo Molnar [this message]
2005-02-11 20:10                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:45           ` 2.6.11-rc3-mm2 Paul Davis
2005-02-14  5:21         ` 2.6.11-rc3-mm2 Werner Almesberger
  -- strict thread matches above, loose matches on Subject: below --
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 20:01   ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-12 22:43   ` 2.6.11-rc3-mm2 Olaf Dietsche
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:02   ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 23:31     ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
2005-02-12 14:53   ` 2.6.11-rc3-mm2 Henning Rohde
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir

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=20050211174905.GC17387@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=hch@infradead.org \
    --cc=jack.oquin@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=paul@linuxaudiosystems.com \
    --cc=rlrevell@joe-job.com \
    /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