From: Hao Li <hao.li@linux.dev>
To: hu.shengming@zte.com.cn
Cc: vbabka@kernel.org, harry@kernel.org, akpm@linux-foundation.org,
cl@gentwo.org, rientjes@google.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhang.run@zte.com.cn, cai.qu@zte.com.cn
Subject: Re: [PATCH v2] mm/slub: free prefilled empty sheaves consistently
Date: Mon, 25 May 2026 14:38:17 +0800 [thread overview]
Message-ID: <ahPsR0YTfhgQnmwQ@fedora> (raw)
In-Reply-To: <20260522145900248m-nBcy07_SCDk2ATDWfmg@zte.com.cn>
On Fri, May 22, 2026 at 02:59:00PM +0800, hu.shengming@zte.com.cn wrote:
> From: Shengming Hu <hu.shengming@zte.com.cn>
>
> Empty sheaves allocated by alloc_empty_sheaf() should be released with
> free_empty_sheaf().
>
> Move the common empty-sheaf initialization into __alloc_empty_sheaf(),
> including the capacity and default pfmemalloc state, and use it for
> oversized prefilled sheaves as well.
>
> This keeps the prefill paths consistent: after flushing an oversized or
> pfmemalloc sheaf, release the now-empty sheaf through free_empty_sheaf()
> instead of kfree().
>
> Signed-off-by: Shengming Hu <hu.shengming@zte.com.cn>
> ---
> Changes in v2:
> - Rework the change as suggested by Harry.
> - Teach __alloc_empty_sheaf() to initialize capacity and pfmemalloc.
> - Allocate oversized prefilled sheaves through __alloc_empty_sheaf().
> - Free flushed oversized and pfmemalloc sheaves through free_empty_sheaf().
> - Link to v1: https://lore.kernel.org/all/20260521195015105Y4zvKHj0TfPZEujixy9Vo@zte.com.cn/
>
> ---
> mm/slub.c | 17 +++++------------
> 1 file changed, 5 insertions(+), 12 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 04692a6f9128..bbe8351f1bfa 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -2782,6 +2782,8 @@ static struct slab_sheaf *__alloc_empty_sheaf(struct kmem_cache *s, gfp_t gfp,
> return NULL;
>
> sheaf->cache = s;
> + sheaf->capacity = capacity;
> + sheaf->pfmemalloc = false;
we could eliminate `sheaf->pfmemalloc = false;` because the allocation use
kzalloc.
>
> stat(s, SHEAF_ALLOC);
>
> @@ -5015,21 +5017,15 @@ kmem_cache_prefill_sheaf(struct kmem_cache *s, gfp_t gfp, unsigned int size)
>
> if (unlikely(size > s->sheaf_capacity)) {
>
> - sheaf = kzalloc_flex(*sheaf, objects, size, gfp);
> + sheaf = __alloc_empty_sheaf(s, gfp, size);
> if (!sheaf)
> return NULL;
>
> stat(s, SHEAF_PREFILL_OVERSIZE);
> - sheaf->cache = s;
> - sheaf->capacity = size;
>
> - /*
> - * we do not need to care about pfmemalloc here because oversize
> - * sheaves area always flushed and freed when returned
> - */
> if (!__kmem_cache_alloc_bulk(s, gfp, size,
> &sheaf->objects[0])) {
> - kfree(sheaf);
> + free_empty_sheaf(s, sheaf);
> return NULL;
> }
>
> @@ -5064,9 +5060,6 @@ kmem_cache_prefill_sheaf(struct kmem_cache *s, gfp_t gfp, unsigned int size)
> sheaf = alloc_empty_sheaf(s, gfp);
>
> if (sheaf) {
> - sheaf->capacity = s->sheaf_capacity;
> - sheaf->pfmemalloc = false;
I think we couldn't delete 'sheaf->pfmemalloc = false;', because the 'sheaf'
pointer here could points to a normal size sheaf via the `if (pcs->spare) {}
else {}` statements above.
> -
> if (sheaf->size < size &&
> __prefill_sheaf_pfmemalloc(s, sheaf, gfp)) {
> sheaf_flush_unused(s, sheaf);
> @@ -5097,7 +5090,7 @@ void kmem_cache_return_sheaf(struct kmem_cache *s, gfp_t gfp,
> if (unlikely((sheaf->capacity != s->sheaf_capacity)
> || sheaf->pfmemalloc)) {
> sheaf_flush_unused(s, sheaf);
> - kfree(sheaf);
> + free_empty_sheaf(s, sheaf);
> return;
> }
>
> --
> 2.25.1
--
Thanks,
Hao
next prev parent reply other threads:[~2026-05-25 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 6:59 [PATCH v2] mm/slub: free prefilled empty sheaves consistently hu.shengming
2026-05-25 6:38 ` Hao Li [this message]
2026-05-25 7:39 ` hu.shengming
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=ahPsR0YTfhgQnmwQ@fedora \
--to=hao.li@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cai.qu@zte.com.cn \
--cc=cl@gentwo.org \
--cc=harry@kernel.org \
--cc=hu.shengming@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@kernel.org \
--cc=zhang.run@zte.com.cn \
/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