From: Lennart Poettering <mzxreary@0pointer.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scheduler: introduce SCHED_RESET_ON_FORK scheduling policy flag, Second try
Date: Wed, 3 Jun 2009 16:07:43 +0200 [thread overview]
Message-ID: <20090603140742.GA22953@tango.0pointer.de> (raw)
In-Reply-To: <20090529083840.GA15516@omega>
On Fri, 29.05.09 10:38, Lennart Poettering (mzxreary@0pointer.de) wrote:
> This patch introduces a new flag SCHED_RESET_ON_FORK which can be passed
> to the kernel via sched_setscheduler(), ORed in the policy parameter. If
> set this will make sure that when the process forks a) the scheduling
> priority is reset to DEFAULT_PRIO if it was higher and b) the scheduling
> policy is reset to SCHED_NORMAL if it was either SCHED_FIFO or SCHED_RR.
[...]
> This current patch compiles but is not otherwise tested. For now, I am
> sending this primarily as a request for comments. So please, I'd love to
> hear your comments!
I have now done some testing to make sure it actually works as
advertised. Everything seems to be fine. For those interested here's a
little test program that verifies that RR scheduling is properly
removed from the child process but is kept enabled in the parent process:
http://0pointer.de/public/reset-on-fork.c
Ingo, how can I bribe you into taking this patch, or at least
commenting on it?
Thanks,
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2009-06-03 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 8:38 [PATCH] scheduler: introduce SCHED_RESET_ON_FORK scheduling policy flag, Second try Lennart Poettering
2009-05-29 9:28 ` Peter Zijlstra
2009-05-29 10:39 ` Lennart Poettering
2009-06-03 14:07 ` Lennart Poettering [this message]
2009-06-05 11:54 ` Ingo Molnar
2009-06-05 14:55 ` Lennart Poettering
2009-06-07 10:11 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-07-03 12:33 Raz
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=20090603140742.GA22953@tango.0pointer.de \
--to=mzxreary@0pointer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 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.