From: Mike Galbraith <efault@gmx.de>
To: Victor henri <nadaeck@hotmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: RE: kernel patch that does wonders
Date: Mon, 21 Mar 2011 03:50:25 +0100 [thread overview]
Message-ID: <1300675825.10813.9.camel@marge.simson.net> (raw)
In-Reply-To: <SNT110-W211BD9DBA57A584FADCEC8A8B20@phx.gbl>
On Sun, 2011-03-20 at 18:18 +0100, Victor henri wrote:
> Hello Mike
>
> >
> > On Sat, 2011-03-19 at 04:44 -0400, Madovsky wrote:
> > > www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=2
> > >
> > > does anybody know this ?
> >
> > Ancient history ;-)
> >
> > > sched_autogroup_enabled=1 gives some miracles apparently
> >
> > No miracles there, it's just group scheduling showing it's good side.
> > It's in 2.6.38 if you want to give it a try.
>
> I just checked the 2.6.38 kernel; the option is not activated by default; Is it worth a try?
> Will it help in any way? Will it lessen latency of a preemt kernel? or at least make it more solid?
It has both positive and negative sides, just like every other option.
There's only one way to find out what it will do for or to you. Turn it
on and find out. I use it daily.. but I turn it off when measuring max
performance, because group scheduling is not free.
If your box is always lightly loaded, you needn't bother. You'll see no
benefit, but will pay the overhead price. If you do interactive stuff
while box is chewing on a hefty load otoh, you may like it quite a lot.
-Mike
prev parent reply other threads:[~2011-03-21 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 8:44 kernel patch that does wonders Madovsky
2011-03-20 5:14 ` Mike Galbraith
2011-03-20 17:18 ` Victor henri
2011-03-21 2:50 ` Mike Galbraith [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=1300675825.10813.9.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=nadaeck@hotmail.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).