From: Marcelo Tosatti <mtosatti@redhat.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Christoph Lameter <cl@linux.com>,
Aaron Tomlin <atomlin@atomlin.com>,
Frederic Weisbecker <frederic@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v2 2/3] vmstat: skip periodic vmstat update for nohz full CPUs
Date: Mon, 5 Jun 2023 16:14:18 -0300 [thread overview]
Message-ID: <ZH40CnznHeBVb/Rb@tpad> (raw)
In-Reply-To: <ZH4wC0gEbsz+H/Aa@dhcp22.suse.cz>
On Mon, Jun 05, 2023 at 08:57:15PM +0200, Michal Hocko wrote:
> > Guest initiated I/O, since the host CPU is isolated.
>
> Make it explicit in the changelog.
I think better use of our time would be to focus on
https://lkml.iu.edu/hypermail/linux/kernel/2209.1/01263.html
1) Operate in terms of add CPU, remove CPU on sysfs (to avoid races).
2) Don't allow all CPUs to be marked as "block_interf".
3) Remove percpu rwsem lock.
> I am just wondering how you can achieve your strict deadlines when IO is
> involved but that is another story I guess.
IO can be submitted when the ELF binary and libraries are read
from the virtual disk, for example.
next prev parent reply other threads:[~2023-06-05 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:57 [PATCH v2 0/3] vmstat bug fixes for nohz_full and isolated CPUs Marcelo Tosatti
2023-06-02 18:57 ` [PATCH v2 1/3] vmstat: allow_direct_reclaim should use zone_page_state_snapshot Marcelo Tosatti
2023-06-02 18:57 ` [PATCH v2 2/3] vmstat: skip periodic vmstat update for nohz full CPUs Marcelo Tosatti
2023-06-05 7:55 ` Michal Hocko
2023-06-05 14:53 ` Marcelo Tosatti
2023-06-05 15:55 ` Michal Hocko
2023-06-05 17:35 ` Marcelo Tosatti
2023-06-05 18:57 ` Michal Hocko
2023-06-05 19:14 ` Marcelo Tosatti [this message]
2023-06-02 18:58 ` [PATCH v2 3/3] mm/vmstat: do not refresh stats for nohz_full CPUs Marcelo Tosatti
2023-06-05 7:59 ` Michal Hocko
2023-06-05 15:43 ` Marcelo Tosatti
2023-06-05 16:10 ` Michal Hocko
2023-06-05 18:14 ` Marcelo Tosatti
2023-06-05 18:25 ` Marcelo Tosatti
2023-06-05 19:12 ` Michal Hocko
2023-06-05 19:44 ` Marcelo Tosatti
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=ZH40CnznHeBVb/Rb@tpad \
--to=mtosatti@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=cl@linux.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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