From: Johannes Weiner <hannes@cmpxchg.org>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, kas@kernel.org,
shakeel.butt@linux.dev, usama.arif@linux.dev,
kernel-team@meta.com
Subject: Re: [PATCH] mm/vmstat: spread vmstat_update requeue across the stat interval
Date: Wed, 1 Apr 2026 10:57:06 -0400 [thread overview]
Message-ID: <ac0yQjSJfhH6nSfy@cmpxchg.org> (raw)
In-Reply-To: <ac0tQb96dK7FKkCQ@gmail.com>
On Wed, Apr 01, 2026 at 07:39:28AM -0700, Breno Leitao wrote:
> Hello Johannes,
>
> On Wed, Apr 01, 2026 at 10:25:35AM -0400, Johannes Weiner wrote:
> > On Wed, Apr 01, 2026 at 06:57:50AM -0700, Breno Leitao wrote:
> > > +static unsigned long vmstat_spread_delay(void)
> > > +{
> > > + unsigned long interval = sysctl_stat_interval;
> > > + unsigned int nr_cpus = num_online_cpus();
> > > +
> > > + if (nr_cpus <= 1)
> > > + return round_jiffies_relative(interval);
> > > +
> > > + /*
> > > + * Spread per-cpu vmstat work evenly across the interval. Don't
> > > + * use round_jiffies_relative() here -- it would snap every CPU
> > > + * back to the same second boundary, defeating the spread.
> > > + */
> > > + return interval + (interval * (smp_processor_id() % nr_cpus)) / nr_cpus;
> >
> > smp_processor_id() <= nr_cpus, so
> >
> > return interval + interval*cpu/nr_cpus
> >
> > should be equivalent, no?
>
> nr_cpus is the number of online CPUs, while smp_processor_id() is the
> CPU id.
>
> If you offline a CPU, then smp_processor_id() might be bigger than
> num_online_cpus()
>
> My goal was to linearly shift the timer and avoid creating gaps when
> removing certain CPUs.
Ah makes sense. Plus you'd spill into the next interval otherwise.
next prev parent reply other threads:[~2026-04-01 14:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 13:57 [PATCH] mm/vmstat: spread vmstat_update requeue across the stat interval Breno Leitao
2026-04-01 14:25 ` Johannes Weiner
2026-04-01 14:39 ` Breno Leitao
2026-04-01 14:57 ` Johannes Weiner [this message]
2026-04-01 14:47 ` Breno Leitao
2026-04-01 15:01 ` Kiryl Shutsemau
2026-04-01 15:23 ` Usama Arif
2026-04-01 15:43 ` Breno Leitao
2026-04-01 15:50 ` Usama Arif
2026-04-01 15:52 ` Breno Leitao
2026-04-01 17:46 ` Vlastimil Babka (SUSE)
2026-04-02 12:40 ` Vlastimil Babka (SUSE)
2026-04-02 13:33 ` Breno Leitao
2026-04-07 15:39 ` Breno Leitao
2026-04-08 10:13 ` Vlastimil Babka (SUSE)
2026-04-08 15:13 ` Breno Leitao
2026-04-08 17:00 ` Breno Leitao
2026-04-09 9:36 ` Vlastimil Babka (SUSE)
2026-04-09 12:27 ` Dmitry Ilvokhin
2026-04-09 9:17 ` Vlastimil Babka (SUSE)
2026-04-02 12:43 ` Dmitry Ilvokhin
2026-04-02 7:18 ` Michal Hocko
2026-04-02 12:49 ` Matthew Wilcox
2026-04-02 13:26 ` Breno Leitao
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=ac0yQjSJfhH6nSfy@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.