From: Mike Galbraith <efault@gmx.de>
To: Trevor Brandt <tjbrandt@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Eric Paris <eparis@redhat.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Glauber Costa <glommer@parallels.com>,
Steven Rostedt <rostedt@goodmis.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, team-fjord@googlegroups.com
Subject: Re: [PATCH] sched: Support compiling out real-time scheduling with REALTIME_SCHED.
Date: Wed, 15 Aug 2012 09:12:20 +0200 [thread overview]
Message-ID: <1345014740.4515.104.camel@marge.simpson.net> (raw)
In-Reply-To: <1344977423-28900-1-git-send-email-tjbrandt@gmail.com>
On Tue, 2012-08-14 at 13:50 -0700, Trevor Brandt wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index 3f42cd6..768dc76 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -27,6 +27,13 @@ config IRQ_WORK
> bool
> depends on HAVE_IRQ_WORK
>
> +config REALTIME_SCHED
> + bool "Realtime Scheduler" if EXPERT
> + default y
> + help
> + This option enables support for the realtime scheduler and the
> + corresponding scheduling classes SCHED_FIFO and SCHED_RR.
> +
> menu "General setup"
>
> config EXPERIMENTAL
If you inverted that, it could be a proper default n new feature [1].
However, if weight loss is the goal, why not go whole hog, and create
sched/thin.c containing no lard... or just integrate an existing thin
scheduler as a config option? Whole body replacement is a very radical
diet, but somehow seems less so than chopping off fingers and toes.
-Mike
(that SMP could select to greatly simplify RT)
next prev parent reply other threads:[~2012-08-15 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 20:50 [PATCH] sched: Support compiling out real-time scheduling with REALTIME_SCHED Trevor Brandt
2012-08-15 7:12 ` Mike Galbraith [this message]
2012-08-15 15:10 ` Josh Triplett
2012-08-16 4:30 ` Mike Galbraith
2012-08-15 15:14 ` Peter Zijlstra
2012-08-15 19:58 ` Steven Rostedt
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=1345014740.4515.104.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=fabio.estevam@freescale.com \
--cc=glommer@parallels.com \
--cc=josh@joshtriplett.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=suresh.b.siddha@intel.com \
--cc=team-fjord@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tjbrandt@gmail.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;
as well as URLs for NNTP newsgroup(s).