From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: ocroquette@free.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Changing RT priority in kernel 2.6 without CAP_SYS_NICE
Date: Tue, 26 Apr 2005 10:13:41 +0200 [thread overview]
Message-ID: <20050426081341.GC31432@elte.hu> (raw)
In-Reply-To: <20050425220040.7e876ce5.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> Ingo Molnar <mingo@elte.hu> wrote:
> >
> > Presently, a process without the capability CAP_SYS_NICE can not change
> > its own policy, which is OK.
> >
> > But it can also not decrease its RT priority (if scheduled with policy
> > SCHED_RR or SCHED_FIFO), which is what this patch changes.
>
> This patch needed some massaging to copt with the changes in
> nice-and-rt-prio-rlimits.patch - please check.
>
> I guess we should merge nice-and-rt-prio-rlimits.patch.
the massaging looks ok - and i agree that we should merge the rt-rlimits
patch.
Ingo
prev parent reply other threads:[~2005-04-26 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 15:38 [PATCH] Changing RT priority in kernel 2.6 without CAP_SYS_NICE Olivier Croquette
2005-04-18 8:07 ` Ingo Molnar
2005-04-26 5:00 ` Andrew Morton
2005-04-26 6:15 ` Olivier Croquette
2005-04-26 8:13 ` Ingo Molnar [this message]
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=20050426081341.GC31432@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocroquette@free.fr \
/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.