From: Ingo Molnar <mingo@elte.hu>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, dhaval@linux.vnet.ibm.com,
aneesh.kumar@in.ibm.com, efault@gmx.de
Subject: Re: 2.6.24-git4+ regression
Date: Mon, 18 Feb 2008 05:28:31 +0100 [thread overview]
Message-ID: <20080218042831.GJ30201@elte.hu> (raw)
In-Reply-To: <20080217202642.GA4327@ics.muni.cz>
* Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> On Thu, Feb 14, 2008 at 10:25:51PM +0530, Srivatsa Vaddagiri wrote:
> > The patch is against 2.6.25-rc1. I would request you to check for
> > difference it makes with CONFIG_FAIR_GROUP_SCHED and
> > CONFIG_FAIR_USER_SCHED turned on.
>
> well, I tried the patch against 2.6.25-rc2-git1. It seems to be better
> but without CONFIG_FAIR_GROUP_SCHED it is still even better.
could you try latest sched-devel.git, does it behave any better? It
includes patches from Peter Zijlstra that should also address latencies
under the group scheduler:
http://people.redhat.com/mingo/sched-devel.git/README
Ingo
next prev parent reply other threads:[~2008-02-18 4:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 13:56 2.6.24-git4+ regression Lukas Hejtmanek
2008-01-31 10:29 ` Ingo Molnar
2008-01-31 10:55 ` Lukas Hejtmanek
2008-02-04 11:17 ` Lukas Hejtmanek
2008-02-04 11:36 ` Peter Zijlstra
2008-02-04 14:36 ` Lukas Hejtmanek
2008-02-04 14:45 ` Peter Zijlstra
2008-02-04 17:00 ` Lukas Hejtmanek
2008-02-04 12:01 ` Ingo Molnar
2008-02-04 12:29 ` Lukas Hejtmanek
2008-02-04 13:04 ` Ingo Molnar
2008-02-04 13:49 ` Lukas Hejtmanek
2008-02-14 16:55 ` Srivatsa Vaddagiri
2008-02-17 20:26 ` Lukas Hejtmanek
2008-02-18 4:28 ` Ingo Molnar [this message]
2008-02-18 7:38 ` Mike Galbraith
2008-02-18 8:20 ` Srivatsa Vaddagiri
2008-02-18 8:36 ` Mike Galbraith
[not found] ` <1203325554.4889.2.camel@homer.simson.net>
[not found] ` <1203345102.5984.1.camel@homer.simson.net>
2008-02-19 8:15 ` Mike Galbraith
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=20080218042831.GJ30201@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=aneesh.kumar@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=xhejtman@ics.muni.cz \
/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.