linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vatika Harlalka <vatikaharlalka@gmail.com>,
	mingo@redhat.com, tglx@linutronix.de, rafael.j.wysocki@intel.com,
	schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org,
	preetium@andrew.cmu.edu, preeti.murthy@gmail.com
Subject: Re: [PATCH 0/2] nohz_full: Offload task_tick to remote housekeeping cpus for nohz_full cpus
Date: Thu, 13 Aug 2015 17:36:15 +0200	[thread overview]
Message-ID: <20150813153614.GD29958@lerouge> (raw)
In-Reply-To: <20150813150545.GD16853@twins.programming.kicks-ass.net>

On Thu, Aug 13, 2015 at 05:05:45PM +0200, Peter Zijlstra wrote:
> On Thu, Aug 13, 2015 at 02:44:02PM +0200, Frederic Weisbecker wrote:
> > On Thu, Aug 13, 2015 at 02:22:23PM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 13, 2015 at 02:55:36PM +0530, Vatika Harlalka wrote:
> > > > This patchset is for offloading task_tick() to a remote housekeeping
> > > > cpu. The larger aim is to stop ticks on nohz_full cpus. For this, extra
> > > > work must be done by housekeeping cpus. So, task_tick is called from a
> > > > delayed workqueue for nohz_full cpus and the work is requeued every second
> > > > for those nohz_full cpus whose ticks are stopped while they are busy. In
> > > > the rest of the cases it will lead to redundant accounting. To facilitate
> > > > this, a new function tick_nohz_remote_tick_stopped is added to indicate
> > > > whether ticks are stopped on a remote cpu.
> > > > Tick related code in core.c is moved to tick.c
> > > 
> > > *sigh* of course you didn't read what I've written on this topic..
> > 
> > What is it? Note Vatika wrote this after my suggestion, so if there is an issue,
> > I'm likely the responsible :-) But I don't recall you opposed to this solution.
> 
> *sigh* of course you _could_ all use Google yourselves.
> 
> Re-read: https://patches.linaro.org/28290/

Sorry, there were dozens of threads about this issue and I got a bit confused.

> 
> I see nothing like the stuff I asked for in here, on top it creates the
> stupid tick.c file.

Right. I initially thought that we should make sched_tick() just work with long delays.
Then tglx suggested the offline idea but I lost track about our conversation.

But yeah making that scheduler_tick() working with long delays sound much better. Certainly
much more work but that's a natural evolution after all. It should pay in longer term.

We can start with update_cpu_load_active() which only works with HZ frequency updates or
nohz idle zero load decay. Now I think that stuff is only used for load balancing. I had
hopes this thing could be removed. I think Alex Shin (IIRC) tried but the patchset didn't
make it.

Thanks.

  reply	other threads:[~2015-08-13 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  9:25 [PATCH 0/2] nohz_full: Offload task_tick to remote housekeeping cpus for nohz_full cpus Vatika Harlalka
2015-08-13  9:25 ` [PATCH 1/2] nohz_full: Move tick related code to tick.c Vatika Harlalka
2015-08-13 12:22 ` [PATCH 0/2] nohz_full: Offload task_tick to remote housekeeping cpus for nohz_full cpus Peter Zijlstra
2015-08-13 12:44   ` Frederic Weisbecker
2015-08-13 15:05     ` Peter Zijlstra
2015-08-13 15:36       ` Frederic Weisbecker [this message]
2015-08-13 19:22         ` Vatika Harlalka
2015-08-20 12:50         ` preetium
2015-08-21 15:55           ` Frederic Weisbecker
     [not found]             ` <CACFGFQQ8mBzS-NhfNsp2nao2XpUksxu3t_Jse2zL2EQHLAK_Hg@mail.gmail.com>
2015-09-11 17:05               ` Vatika Harlalka

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=20150813153614.GD29958@lerouge \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=preeti.murthy@gmail.com \
    --cc=preetium@andrew.cmu.edu \
    --cc=rafael.j.wysocki@intel.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=vatikaharlalka@gmail.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;
as well as URLs for NNTP newsgroup(s).