linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Christoph Lameter <cl@gentwo.de>,
	frederic@kernel.org, tglx@linutronix.de, mingo@kernel.org,
	pauld@redhat.com, neelx@redhat.com, oleksandr@natalenko.name,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v3] tick/sched: Ensure quiet_vmstat() is called when the idle tick was stopped too
Date: Mon, 25 Apr 2022 16:21:59 -0300	[thread overview]
Message-ID: <Ymb018EaVlOUfx87@fuller.cnet> (raw)
In-Reply-To: <20220425141717.vw2jfnn3zp6c5ib2@ava.usersys.com>

On Mon, Apr 25, 2022 at 03:17:17PM +0100, Aaron Tomlin wrote:
> On Mon 2022-04-25 15:27 +0200, Peter Zijlstra wrote:
> > On Mon, Apr 25, 2022 at 02:09:06PM +0200, Christoph Lameter wrote:
> > > On Mon, 25 Apr 2022, Aaron Tomlin wrote:
> > > 
> > > > Yes, in the context of nohz, this patch should ensure it, if required, when
> > > > the idle tick is to be stopped.
> > > 
> > > What I said was that it is generally useful. Even in the non NOHZ case.
> > > 
> > > Folding the vmstat diffs *always* when entering idle prevents unnecessary
> > > wakeups and processing in the future and also provides more accurate
> > > counters for the VM allowing better decision to be made on reclaim.
> > 
> > I'm thinking you're going to find a ton of regressions if you try it
> > though; some workloads go idle *very* shortly, doing all this accounting
> > is going to be counter-productive.
> 
> Hi Peter, Christoph,
> 
> Indeed. Which was why I decided, initially, against the general-purpose
> case/or approach. Personally, I would prefer to keep this somewhat
> restrictive to nohz.

Is there anything that prevents a nohz full CPU from running an
application with short and frequent idling?

Note:

commit a5183862e76fdc25f36b39c2489b816a5c66e2e5
Author: Yunfeng Ye <yeyunfeng@huawei.com>
Date:   Thu May 13 01:29:16 2021 +0200

    tick/nohz: Conditionally restart tick on idle exit
    
    In nohz_full mode, switching from idle to a task will unconditionally
    issue a tick restart. If the task is alone in the runqueue or is the
    highest priority, the tick will fire once then eventually stop. But that
    alone is still undesired noise.
    
    Therefore, only restart the tick on idle exit when it's strictly
    necessary.
    
    Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
    Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    Acked-by: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20210512232924.150322-3-frederic@kernel.org




  reply	other threads:[~2022-04-25 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 19:36 [RFC PATCH v3] tick/sched: Ensure quiet_vmstat() is called when the idle tick was stopped too Aaron Tomlin
2022-04-25  7:23 ` Christoph Lameter
2022-04-25 11:39   ` Aaron Tomlin
2022-04-25 12:09     ` Christoph Lameter
2022-04-25 13:27       ` Peter Zijlstra
2022-04-25 14:06         ` Christoph Lameter
2022-04-25 14:51           ` Aaron Tomlin
2022-04-25 14:57           ` Marcelo Tosatti
2022-04-25 14:17         ` Aaron Tomlin
2022-04-25 19:21           ` Marcelo Tosatti [this message]
2022-04-27 11:50             ` Aaron Tomlin
2022-04-27 14:40               ` Thomas Gleixner
2022-04-27 14:49                 ` Aaron Tomlin
2022-04-28 18:10 ` Marcelo Tosatti
2022-05-04  9:32   ` Aaron Tomlin

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=Ymb018EaVlOUfx87@fuller.cnet \
    --to=mtosatti@redhat.com \
    --cc=atomlin@redhat.com \
    --cc=cl@gentwo.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=neelx@redhat.com \
    --cc=oleksandr@natalenko.name \
    --cc=pauld@redhat.com \
    --cc=peterz@infradead.org \
    --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 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).