From: Aaron Tomlin <atomlin@atomlin.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Aaron Tomlin <atomlin@redhat.com>, Phil Auld <pauld@redhat.com>,
tglx@linutronix.de, mingo@kernel.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH] tick/sched: Ensure quiet_vmstat() is called when the idle tick was stopped too
Date: Thu, 17 Feb 2022 14:45:24 +0000 [thread overview]
Message-ID: <20220217144524.el7lwi45hwsf3ef2@ava.usersys.com> (raw)
In-Reply-To: <20220217125731.GA744754@lothringen>
On Thu 2022-02-17 13:57 +0100, Frederic Weisbecker wrote:
> Hmm, but does it matter? The issue seem to be that we can enter in idle loop without
> flushing vmstat. Or am I missing something else?
Frederic,
Yes, this is indeed the concern. So, the idea I had was to invoke
quiet_vmstat() regardless if the tick was stopped or not. If I understand
correctly, this should resolve the issue. Furthermore, folding of all
outstanding differentials will only occur when required. Thus performance
should be negligible.
Kind regards,
--
Aaron Tomlin
next prev parent reply other threads:[~2022-02-17 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:43 [RFC PATCH] tick/sched: Ensure quiet_vmstat() is called when the idle tick was stopped too Aaron Tomlin
2022-02-03 22:22 ` Phil Auld
2022-02-16 14:34 ` Aaron Tomlin
2022-02-16 21:20 ` Phil Auld
2022-02-17 12:57 ` Frederic Weisbecker
2022-02-17 14:45 ` Aaron Tomlin [this message]
2022-02-17 12:47 ` Frederic Weisbecker
2022-02-17 14:26 ` Aaron Tomlin
2022-02-17 16:32 ` Frederic Weisbecker
2022-02-18 12:54 ` Aaron Tomlin
2022-02-19 15:46 ` Aaron Tomlin
2022-02-24 12:27 ` Marcelo Tosatti
2022-02-24 12:30 ` Marcelo Tosatti
2022-02-24 13:01 ` Aaron Tomlin
2022-02-24 12:37 ` Marcelo Tosatti
2022-02-24 13:00 ` Aaron Tomlin
2022-02-24 13:14 ` Marcelo Tosatti
2022-02-24 13:28 ` Aaron Tomlin
2022-02-24 13:40 ` Marcelo Tosatti
2022-02-24 13:44 ` Aaron Tomlin
2022-03-31 14:33 ` 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=20220217144524.el7lwi45hwsf3ef2@ava.usersys.com \
--to=atomlin@atomlin.com \
--cc=atomlin@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pauld@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 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).