From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: venkatesh.pallipadi@intel.com
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Gautham R Shenoy <ego@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [patch 2/2] RFC sched: Scale the nohz_tracker logic by making it per NUMA node
Date: Thu, 18 Jun 2009 00:51:16 +0530 [thread overview]
Message-ID: <20090617192116.GI7961@dirshya.in.ibm.com> (raw)
In-Reply-To: <20090617182741.107659000@intel.com>
* venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com> [2009-06-17 11:26:51]:
> Having one idle CPU doing the rebalancing for all the idle CPUs in
> nohz mode does not scale well with increasing number of cores and
> sockets. Make the nohz_tracker per NUMA node. This results in multiple
> idle load balancing happening at NUMA node level and idle load balancer
> only does the rebalance domain among all the other nohz CPUs in that
> NUMA node.
This is a good optimisations but maybe an overkill for single chip
NUMA node machines like a two socket Nehalems or Optrons.
Some method to create load balancer group based on the scale of the
machine will be good.
--Vaidy
next prev parent reply other threads:[~2009-06-17 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 18:26 [patch 0/2] RFC sched: Change nohz ilb logic from poll to push model venkatesh.pallipadi
2009-06-17 18:26 ` [patch 1/2] RFC sched: Change the nohz ilb logic from pull " venkatesh.pallipadi
2009-06-17 18:26 ` [patch 2/2] RFC sched: Scale the nohz_tracker logic by making it per NUMA node venkatesh.pallipadi
2009-06-17 19:21 ` Vaidyanathan Srinivasan [this message]
2009-06-17 19:16 ` [patch 0/2] RFC sched: Change nohz ilb logic from poll to push model Vaidyanathan Srinivasan
2009-06-18 23:41 ` Pallipadi, Venkatesh
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=20090617192116.GI7961@dirshya.in.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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