From: Peter Zijlstra <peterz@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: vatsa@linux.vnet.ibm.com, dhaval@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [RFT][PATCH] sched: scale sysctl_sched_shares_ratelimit with nr_cpus
Date: Wed, 30 Jul 2008 12:32:29 +0200 [thread overview]
Message-ID: <1217413949.8157.12.camel@twins> (raw)
In-Reply-To: <20080730.032930.55051878.davem@davemloft.net>
On Wed, 2008-07-30 at 03:29 -0700, David Miller wrote:
> From: Peter Zijlstra <peterz@infradead.org>
> Date: Wed, 30 Jul 2008 12:25:11 +0200
>
> > Dhaval, Vatsa,
> >
> > Could you guys give this patch a spin on the big iron and possibly tune
> > the default shares_ratelimit value to give satisfactory fairness on your
> > large machines while considering the overhead?
> >
> >
> > ---
> > Subject: sched: scale sysctl_sched_shares_ratelimit with nr_cpus
> >
> > David reported that his Niagra spend a little too much time in
> > tg_shares_up(), which considering he has a large cpu count makes sense.
> >
> > So scale the ratelimit value with the number of cpus like we do for
> > other controls as well.
> >
> > Reported-by: David Miller <davem@davemloft.net>
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> This turned out to be a false theory, and the lockdep problem I
> reported the past few days was the real culprit.
>
> The rebalancing et al. showing up in my debugging dumps was
> just chance and not even consistent.
Ah, still I think the proposed change makes sense, but lets wait for
some test results from Dhaval and or Vatsa.. ;-)
next parent reply other threads:[~2008-07-30 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1217413511.8157.7.camel@twins>
[not found] ` <20080730.032930.55051878.davem@davemloft.net>
2008-07-30 10:32 ` Peter Zijlstra [this message]
2008-07-30 10:27 [RFT][PATCH] sched: scale sysctl_sched_shares_ratelimit with nr_cpus Peter Zijlstra
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=1217413949.8157.12.camel@twins \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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