From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, "Ingo Molnar" <mingo@elte.hu>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
=?iso-8859-1?Q?Michel=2ED=E4nzer_=3Cmichel=40tungstengraphics=2Ecom=3E?=.=?iso-8859-1?B?QHNub3d5LmluLmlibS5jb20=?=@snowy.in.ibm.com,
"Michel.Dänzer" <michel@tungstengraphics.com>
Subject: Re: ppc32: Weird process scheduling behaviour with 2.6.24-rc
Date: Sat, 26 Jan 2008 14:56:45 +0530 [thread overview]
Message-ID: <20080126092644.GA1044@linux.vnet.ibm.com> (raw)
In-Reply-To: <1201324552.6815.165.camel@pasglop>
On Sat, Jan 26, 2008 at 04:15:52PM +1100, Benjamin Herrenschmidt wrote:
> > Michel,
> > You had reported that commit 810e95ccd58d91369191aa4ecc9e6d4a10d8d0c8
> > was the cause for this bad behavior. Do you see behavior change (from good->bad)
> > immediately after applying that patch during your bisect process?
>
> Also Michel, double check your .config in both cases.
And also Michel whether CONFIG_FAIR_GROUP_SCHED + CONFIG_FAIR_CGROUP_SCHED
gives more or less same desktop exp as !CONFIG_FAIR_GROUP_SCHED pls!
> > I would prefer to have CONFIG_FAIR_GROUP_SCHED +
> > CONFIG_FAIR_CGROUP_SCHED on by default. Can you pls let me know how you
> > think is the desktop experience with that combination?
>
> I'm going to give that a try but unfortunately, it will have to wait
> until I'm back from LCA in a bit more than a week.
--
Regards,
vatsa
next prev parent reply other threads:[~2008-01-26 9:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 12:34 ppc32: Weird process scheduling behaviour with 2.6.24-rc Michel Dänzer
2008-01-22 14:56 ` Michel Dänzer
2008-01-23 12:18 ` Michel Dänzer
2008-01-23 12:36 ` Peter Zijlstra
2008-01-23 13:14 ` Michel Dänzer
2008-01-24 8:18 ` Benjamin Herrenschmidt
2008-01-24 8:46 ` Benjamin Herrenschmidt
2008-01-25 10:57 ` Michel Dänzer
2008-01-23 12:42 ` Peter Zijlstra
2008-01-25 6:54 ` Benjamin Herrenschmidt
2008-01-25 7:03 ` Benjamin Herrenschmidt
2008-01-25 7:25 ` Benjamin Herrenschmidt
2008-01-25 8:50 ` Peter Zijlstra
2008-01-26 4:07 ` Srivatsa Vaddagiri
2008-01-26 4:13 ` Benjamin Herrenschmidt
2008-01-26 5:07 ` Srivatsa Vaddagiri
2008-01-26 5:15 ` Benjamin Herrenschmidt
2008-01-26 9:26 ` Srivatsa Vaddagiri [this message]
2008-01-26 5:07 ` Srivatsa Vaddagiri
2008-01-27 16:13 ` Michel Dänzer
2008-01-28 4:25 ` Benjamin Herrenschmidt
2008-01-28 8:16 ` Michel Dänzer
2008-01-28 8:50 ` Peter Zijlstra
2008-01-28 9:14 ` Michel Dänzer
2008-01-28 12:11 ` Srivatsa Vaddagiri
2008-01-28 12:32 ` Ingo Molnar
2008-01-28 12:53 ` Peter Zijlstra
2008-01-28 12:56 ` Ingo Molnar
2008-01-29 10:14 ` Michel Dänzer
2008-01-28 13:11 ` Srivatsa Vaddagiri
2008-01-25 11:34 ` Michel Dänzer
2008-01-25 15:04 ` Michel Dänzer
2008-01-25 21:10 ` Benjamin Herrenschmidt
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=20080126092644.GA1044@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc==?iso-8859-1?Q?Michel=2ED=E4nzer_=3Cmichel=40tungstengraphics=2Ecom=3E?=.=?iso-8859-1?B?QHNub3d5LmluLmlibS5jb20=?=@snowy.in.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michel@tungstengraphics.com \
--cc=mingo@elte.hu \
/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).