From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linuxppc-dev@ozlabs.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
michel@tungstengraphics.com
Subject: Re: ppc32: Weird process scheduling behaviour with 2.6.24-rc
Date: Mon, 28 Jan 2008 18:41:35 +0530 [thread overview]
Message-ID: <20080128131135.GJ1044@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080128123253.GA32496@elte.hu>
On Mon, Jan 28, 2008 at 01:32:53PM +0100, Ingo Molnar wrote:
> * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > > * With CONFIG_FAIR_USER_SCHED disabled, there are severe
> > > interactivity hickups with a niced CPU hog and top running. This
> > > started with commit 810e95ccd58d91369191aa4ecc9e6d4a10d8d0c8.
> >
> > The revert at the bottom causes the wakeup granularity to shrink for +
> > nice and to grow for - nice. That is, it becomes easier to preempt a +
> > nice task, and harder to preempt a - nice task.
>
> i think it would be OK to do half of this: make it easier to preempt a
> +nice task.
Hmm .. I doubt whether that would help Michel's case, as he seems to be running
+niced tasks and having problems getting control over his desktop.
Something is basically wrong here ..
> Michel, do you really need the -nice portion as well? It's
> not a problem to super-preempt positively reniced tasks, but it can be
> quite annoying if negatively reniced tasks have super-slices.
--
Regards,
vatsa
next prev parent reply other threads:[~2008-01-28 12:57 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
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 [this message]
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=20080128131135.GJ1044@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--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).