From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Michel.=?iso-8859-1?Q?D=E4nzer_=3Cmichel=40tungstengraphics=2Ecom=3E?=@snowy.in.ibm.com
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linuxppc-dev@ozlabs.org
Subject: Re: ppc32: Weird process scheduling behaviour with 2.6.24-rc
Date: Mon, 28 Jan 2008 17:41:49 +0530 [thread overview]
Message-ID: <20080128121149.GA29867@linux.vnet.ibm.com> (raw)
In-Reply-To: <1201511673.5923.46.camel@thor.sulgenrain.local>
On Mon, Jan 28, 2008 at 10:14:33AM +0100, Michel Dänzer wrote:
> > > * With CONFIG_FAIR_USER_SCHED enabled, X becomes basically
> > > unusable with a niced CPU hog, with or without top running. I
> > > don't know when this started, possibly when this option was
> > > first introduced.
> >
> > Srivatsa found an issue that might explain the very bad behaviour under
> > group scheduling. But I gather you're not at all interested in this
> > feature?
>
> That's right, but it's good to hear you have a lead there as well, and
> if you can't find any interested testers, let me know and I'll try.
Michel,
Thanks for offering to test! The issue I found wrt preemption latency
(when FAIR_USER_SCHED is turned on) is explained here:
http://marc.info/?l=linux-kernel&m=120148675326287
Does the patch in that URL help bring FAIR_USER_SCHED interactivity to the same
level as !FAIR_USER_SCHED?
--
Regards,
vatsa
next prev parent reply other threads:[~2008-01-28 11:58 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
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 [this message]
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=20080128121149.GA29867@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=Michel.=?iso-8859-1?Q?D=E4nzer_=3Cmichel=40tungstengraphics=2Ecom=3E?=@snowy.in.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linuxppc-dev@ozlabs.org \
--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 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.