From: Frederic Weisbecker <fweisbec@gmail.com>
To: mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, riel@redhat.com,
torvalds@linux-foundation.org, peterz@infradead.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/fair: Spare idle load balancing on nohz_full CPUs
Date: Thu, 22 Jun 2017 15:52:05 +0200 [thread overview]
Message-ID: <20170622135203.GA21172@lerouge> (raw)
In-Reply-To: <tip-387bc8b5536eeb0a92f4b4ab553539eaea2ac0ba@git.kernel.org>
Hi Ingo,
On Thu, Jun 22, 2017 at 04:11:53AM -0700, tip-bot for Frederic Weisbecker wrote:
> Commit-ID: 387bc8b5536eeb0a92f4b4ab553539eaea2ac0ba
> Gitweb: http://git.kernel.org/tip/387bc8b5536eeb0a92f4b4ab553539eaea2ac0ba
> Author: Frederic Weisbecker <fweisbec@gmail.com>
> AuthorDate: Mon, 19 Jun 2017 04:12:02 +0200
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Thu, 22 Jun 2017 11:30:02 +0200
>
> sched/fair: Spare idle load balancing on nohz_full CPUs
Thanks for applying the series! The two other patches are indeed good but
Rik and Mike have mitigated feelings about this very patch. I think we need to decouple
housekeeping from nohz_full before applying it. Is it possible to set it aside
for now?
Thanks!
next prev parent reply other threads:[~2017-06-22 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 2:11 [PATCH 0/3] sched: A few nohz_full improvements Frederic Weisbecker
2017-06-19 2:12 ` [PATCH 1/3] sched/loadavg: Generalize idle naming to nohz Frederic Weisbecker
2017-06-20 17:38 ` Rik van Riel
2017-06-22 11:10 ` [tip:sched/core] sched/loadavg: Generalize "_idle" naming to "_nohz" tip-bot for Frederic Weisbecker
2017-06-19 2:12 ` [PATCH 2/3] nohz: Move idle balancer registration to idle path Frederic Weisbecker
2017-06-20 17:39 ` Rik van Riel
2017-06-22 11:11 ` [tip:sched/core] nohz: Move idle balancer registration to the " tip-bot for Frederic Weisbecker
2017-06-19 2:12 ` [PATCH 3/3] sched: Spare idle load balancing on nohz_full CPUs Frederic Weisbecker
2017-06-20 17:42 ` Rik van Riel
2017-06-20 19:06 ` Mike Galbraith
2017-06-21 13:23 ` Frederic Weisbecker
2017-06-20 20:26 ` Frederic Weisbecker
2017-06-22 11:11 ` [tip:sched/core] sched/fair: " tip-bot for Frederic Weisbecker
2017-06-22 13:52 ` Frederic Weisbecker [this message]
2017-06-22 19:47 ` Ingo Molnar
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=20170622135203.GA21172@lerouge \
--to=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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).