From: "Zi Yan" <ziy@nvidia.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
"William Kucharski" <william.kucharski@oracle.com>,
"David Hildenbrand" <david@kernel.org>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
"Nico Pache" <nico.pache@linux.dev>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Dev Jain" <dev.jain@arm.com>, "Barry Song" <baohua@kernel.org>,
"Lance Yang" <lance.yang@linux.dev>,
"Usama Arif" <usama.arif@linux.dev>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [PATCH v2 2/2] xarray: honor XA_FLAGS_ACCOUNT in xas_split_alloc()
Date: Mon, 03 Aug 2026 11:12:10 -0400 [thread overview]
Message-ID: <DKFELWPHSJNO.3GGVW270HENEG@nvidia.com> (raw)
In-Reply-To: <am2-HmShC6VXP_-G@lucifer>
On Sat Aug 1, 2026 at 5:38 AM EDT, Lorenzo Stoakes (ARM) wrote:
> On Thu, Jul 30, 2026 at 10:18:01PM -0400, Zi Yan wrote:
>> XArray operations that allocate xa_nodes, such as xas_nomem() and
>> xas_alloc(), add __GFP_ACCOUNT when the array has XA_FLAGS_ACCOUNT set.
>> This charges the allocated memory and avoids the workingset convergence
>> issue described by commit 7b785645e8f13 ("mm: fix page cache convergence
>> regression").
>>
>> xas_split_alloc() does not have that flag. Add it when necessary.
>
> Nit but maybe 'split' rather than 'have'?
Yeah, the sentence is pretty vague. How about?
xas_split_alloc() does not add _GFP_ACCOUNT when XA_FLAGS_ACCOUNT is
present. Add code to do it.
>
>>
>> Fixes: 6b24ca4a1a8d4 ("mm: Use multi-index entries in the page cache")
>
> Cc: stable?
This should go along with Patch 1. So if we decided to backport Patch 1,
I will Cc: stable for this as well.
>
>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>
> Makes sense to me so:
>
> Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
>
>> ---
>> lib/xarray.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/lib/xarray.c b/lib/xarray.c
>> index 9a8b4916540cf..bfe7bef80f34e 100644
>> --- a/lib/xarray.c
>> +++ b/lib/xarray.c
>> @@ -1053,6 +1053,9 @@ void xas_split_alloc(struct xa_state *xas, void *entry, unsigned int order,
>> if (xas->xa_shift + XA_CHUNK_SHIFT > order)
>> return;
>>
>> + if (xas->xa->xa_flags & XA_FLAGS_ACCOUNT)
>> + gfp |= __GFP_ACCOUNT;
>> +
>
> This is some confluence of flags :) I wonder if there are other places we've
> missed setting this for?
I did check the whole lib/xarray.c. xas_nomem(), __xas_nomem(),
xas_alloc(), xas_try_split(), and xas_split_alloc() are the ones using
gfp to allocate memory. Only xas_split_alloc() does not add
__GFP_ACCOUNT for XA_FLAGS_ACCOUNT.
--
Best Regards,
Yan, Zi
prev parent reply other threads:[~2026-08-03 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 2:17 [PATCH v2 0/2] Honor XA_FLAGS_ACCOUNT in xas_split_alloc() and charge to folio's memcg Zi Yan
2026-07-31 2:18 ` [PATCH v2 1/2] mm/huge_memory: use folio's memcg inside __folio_split() Zi Yan
2026-08-01 6:57 ` Johannes Weiner
2026-08-01 9:36 ` Lorenzo Stoakes (ARM)
2026-08-03 15:02 ` Zi Yan
2026-08-03 15:07 ` Lorenzo Stoakes (ARM)
2026-08-03 15:23 ` Zi Yan
2026-08-03 17:25 ` Kairui Song
2026-08-03 17:55 ` Zi Yan
2026-08-04 3:09 ` Kairui Song
2026-08-05 14:36 ` Zi Yan
2026-08-05 10:52 ` Lorenzo Stoakes (ARM)
2026-08-04 20:47 ` Johannes Weiner
2026-08-04 21:27 ` Andrew Morton
2026-08-03 2:39 ` Baolin Wang
2026-07-31 2:18 ` [PATCH v2 2/2] xarray: honor XA_FLAGS_ACCOUNT in xas_split_alloc() Zi Yan
2026-08-01 6:58 ` Johannes Weiner
2026-08-01 9:38 ` Lorenzo Stoakes (ARM)
2026-08-03 15:12 ` Zi Yan [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=DKFELWPHSJNO.3GGVW270HENEG@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.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.