From: Johannes Weiner <hannes@cmpxchg.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Michal Hocko <mhocko@suse.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: vmalloc: streamline vmalloc memory accounting
Date: Mon, 23 Feb 2026 15:19:20 -0500 [thread overview]
Message-ID: <aZy2SHbXi6qdGS0a@cmpxchg.org> (raw)
In-Reply-To: <aZxymBwx67pMn1ZP@pc636>
On Mon, Feb 23, 2026 at 04:30:32PM +0100, Uladzislau Rezki wrote:
> On Fri, Feb 20, 2026 at 02:10:34PM -0500, Johannes Weiner wrote:
> > @@ -3655,6 +3649,8 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
> > continue;
> > }
> >
> > + mod_node_page_state(page, NR_VMALLOC, 1 << large_order);
> > +
> > split_page(page, large_order);
> > for (i = 0; i < (1U << large_order); i++)
> > pages[nr_allocated + i] = page + i;
> > @@ -3675,6 +3671,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
> > if (!order) {
> > while (nr_allocated < nr_pages) {
> > unsigned int nr, nr_pages_request;
> > + int i;
> >
> > /*
> > * A maximum allowed request is hard-coded and is 100
> > @@ -3698,6 +3695,9 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
> > nr_pages_request,
> > pages + nr_allocated);
> >
> > + for (i = nr_allocated; i < nr_allocated + nr; i++)
> > + inc_node_page_state(pages[i], NR_VMALLOC);
> > +
> > nr_allocated += nr;
> >
> > /*
> > @@ -3722,6 +3722,8 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
> > if (unlikely(!page))
> > break;
> >
> > + mod_node_page_state(page, NR_VMALLOC, 1 << order);
> > +
> > /*
> Can we move *_node_page_stat() to the end of the vm_area_alloc_pages()?
>
> Or mod_node_page_state in first place should be invoked on high-order
> page before split(to avoid of looping over small pages afterword)?
>
> I mean it would be good to place to the one solid place. If it is possible
> of course.
Note that the top one in the fast path IS called before the
split. We're accounting in the same step size as the page allocator
can give us.
In the fallback paths (bulk allocator, and one-by-one loop), the issue
is that the individual pages could be coming from different nodes, so
they need to bump different counters. One possible solution would be
to remember the last node and accumulate until it differs, then flush:
fallback_loop() {
page = alloc_pages();
nid = page_to_nid(page);
if (nid != last_nid) {
if (node_count) {
mod_node_page_state(...);
node_count = 0;
}
last_nid = nid;
}
}
if (node_count)
mod_node_page_state(...);
But it IS the slow path, and these are fairly cheap per-cpu
counters. Especially compared to the cost of calling into the
allocator. So I'm not sure it's worth it... What do you think?
prev parent reply other threads:[~2026-02-23 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 19:10 Johannes Weiner
2026-02-20 19:10 ` [PATCH 2/2] mm: memcontrol: switch to native NR_VMALLOC vmstat counter Johannes Weiner
2026-02-20 22:15 ` Shakeel Butt
2026-02-23 15:12 ` Uladzislau Rezki
2026-02-20 22:09 ` [PATCH 1/2] mm: vmalloc: streamline vmalloc memory accounting Shakeel Butt
2026-02-23 15:58 ` Johannes Weiner
2026-02-23 15:30 ` Uladzislau Rezki
2026-02-23 20:19 ` Johannes Weiner [this message]
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=aZy2SHbXi6qdGS0a@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=urezki@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