All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Luiz Capitulino <lcapitulino@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Chris Metcalf <cmetcalf@mellanox.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christoph Lameter <cl@linux.com>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
	Wanpeng Li <kernellwp@gmail.com>
Subject: Re: [RFC PATCH 7/9] housekeeping: Use own boot option, independant from nohz
Date: Mon, 14 Aug 2017 20:29:46 +0200	[thread overview]
Message-ID: <1502735386.31351.61.camel@gmx.de> (raw)
In-Reply-To: <20170814133440.3dc31bad@redhat.com>

On Mon, 2017-08-14 at 13:34 -0400, Luiz Capitulino wrote:
> On Mon, 14 Aug 2017 19:01:09 +0200
> 
> > What is the source of the load balancing inducing such latency when a single
> > task is affine to a CPU? If this is idle load balancing, it is now affine to
> > housekeepers. If this is task wakeup then it's suprising because select_task_rq()
> > is optimized toward single CPU affinity.
> 
> I guess it was idle load balancing, but I don't remember because this
> was a few years ago. I think this might be reproducible without using
> isolcpus=. I'll give it a try shortly and let you know.

idle_balance() can swamp other noise by a couple orders of magnitude,

	-Mike

  reply	other threads:[~2017-08-14 18:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 13:21 [RFC PATCH 0/9] Introduce housekeeping subsystem Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 1/9] housekeeping: Move housekeeping related code to its own file Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 2/9] watchdog: Use housekeeping_cpumask() instead of ad-hoc version Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 3/9] housekeeping: Provide a dynamic off-case to housekeeping_any_cpu() Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 4/9] housekeeping: Make housekeeping cpumask private Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 5/9] housekeeping: Use its own static key Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 6/9] housekeeping: Rename is_housekeeping_cpu to housekeeping_cpu Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 7/9] housekeeping: Use own boot option, independant from nohz Frederic Weisbecker
2017-08-11 19:09   ` Luiz Capitulino
2017-08-12 14:10     ` Frederic Weisbecker
2017-08-13 15:13       ` Luiz Capitulino
2017-08-14 17:01         ` Frederic Weisbecker
2017-08-14 17:34           ` Luiz Capitulino
2017-08-14 18:29             ` Mike Galbraith [this message]
2017-08-15 13:07               ` Frederic Weisbecker
2017-08-15 15:15                 ` Mike Galbraith
2017-08-15 15:30                   ` Paul E. McKenney
2017-08-15 15:52                     ` Christopher Lameter
2017-08-15 15:57                       ` Mike Galbraith
2017-08-15 16:26                         ` Christopher Lameter
2017-08-16 18:00                           ` Mike Galbraith
2017-08-15 15:53                     ` Mike Galbraith
2017-07-21 13:21 ` [RFC PATCH 8/9] housekeeping: Move it under own config, independant from NO_HZ Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 9/9] workqueue: Affine unbound workqueues to housekeeping cpumask Frederic Weisbecker
2017-07-21 19:48 ` [RFC PATCH 0/9] Introduce housekeeping subsystem Chris Metcalf
2017-08-10 12:54   ` Frederic Weisbecker
2017-08-10 13:57     ` Chris Metcalf
2017-08-11  6:36       ` Mike Galbraith
2017-08-11 15:01         ` Frederic Weisbecker
2017-08-11 19:22           ` Luiz Capitulino
2017-08-11 15:08         ` Chris Metcalf
2017-08-11 15:35           ` Christopher Lameter
2017-08-11 15:50             ` Chris Metcalf

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=1502735386.31351.61.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=cl@linux.com \
    --cc=cmetcalf@mellanox.com \
    --cc=fweisbec@gmail.com \
    --cc=kernellwp@gmail.com \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    /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.