From: Vlastimil Babka <vbabka@suse.cz>
To: Harry Yoo <harry.yoo@oracle.com>, akpm@linux-foundation.org
Cc: andreyknvl@gmail.com, cl@gentwo.org, dvyukov@google.com,
glider@google.com, hannes@cmpxchg.org, linux-mm@kvack.org,
mhocko@kernel.org, muchun.song@linux.dev, rientjes@google.com,
roman.gushchin@linux.dev, ryabinin.a.a@gmail.com,
shakeel.butt@linux.dev, surenb@google.com,
vincenzo.frascino@arm.com, yeoreum.yun@arm.com, tytso@mit.edu,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
hao.li@linux.dev
Subject: Re: [PATCH V6 8/9] mm/slab: move [__]ksize and slab_ksize() to mm/slub.c
Date: Tue, 13 Jan 2026 13:44:45 +0100 [thread overview]
Message-ID: <2cdff2ed-a45d-47e9-94ef-f8ecd178bbae@suse.cz> (raw)
In-Reply-To: <20260113061845.159790-9-harry.yoo@oracle.com>
On 1/13/26 7:18 AM, Harry Yoo wrote:
> To access SLUB's internal implementation details beyond cache flags in
> ksize(), move __ksize(), ksize(), and slab_ksize() to mm/slub.c.
>
> Signed-off-by: Harry Yoo <harry.yoo@oracle.com>
> ---
> mm/slab.h | 25 --------------
> mm/slab_common.c | 61 ----------------------------------
> mm/slub.c | 86 ++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 86 insertions(+), 86 deletions(-)
>
> diff --git a/mm/slab.h b/mm/slab.h
> index 5176c762ec7c..957586d68b3c 100644
> --- a/mm/slab.h
> +++ b/mm/slab.h
> @@ -665,31 +665,6 @@ void kvfree_rcu_cb(struct rcu_head *head);
>
> size_t __ksize(const void *objp);
>
> -static inline size_t slab_ksize(const struct kmem_cache *s)
> -{
> -#ifdef CONFIG_SLUB_DEBUG
> - /*
> - * Debugging requires use of the padding between object
> - * and whatever may come after it.
> - */
> - if (s->flags & (SLAB_RED_ZONE | SLAB_POISON))
> - return s->object_size;
> -#endif
> - if (s->flags & SLAB_KASAN)
> - return s->object_size;
> - /*
> - * If we have the need to store the freelist pointer
> - * back there or track user information then we can
> - * only use the space before that information.
> - */
> - if (s->flags & (SLAB_TYPESAFE_BY_RCU | SLAB_STORE_USER))
> - return s->inuse;
> - /*
> - * Else we can use all the padding etc for the allocation
> - */
> - return s->size;
> -}
> -
> static inline unsigned int large_kmalloc_order(const struct page *page)
> {
> return page[1].flags.f & 0xff;
> diff --git a/mm/slab_common.c b/mm/slab_common.c
> index c4cf9ed2ec92..aed91fd6fd10 100644
> --- a/mm/slab_common.c
> +++ b/mm/slab_common.c
> @@ -983,43 +983,6 @@ void __init create_kmalloc_caches(void)
> 0, SLAB_NO_MERGE, NULL);
> }
>
> -/**
> - * __ksize -- Report full size of underlying allocation
> - * @object: pointer to the object
> - *
> - * This should only be used internally to query the true size of allocations.
> - * It is not meant to be a way to discover the usable size of an allocation
> - * after the fact. Instead, use kmalloc_size_roundup(). Using memory beyond
> - * the originally requested allocation size may trigger KASAN, UBSAN_BOUNDS,
> - * and/or FORTIFY_SOURCE.
> - *
> - * Return: size of the actual memory used by @object in bytes
> - */
> -size_t __ksize(const void *object)
Think it could be also static and not in slab.h? I'll make that change
locally.
next prev parent reply other threads:[~2026-01-13 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 6:18 [PATCH V6 0/9] mm/slab: reduce slab accounting memory overhead by allocating slabobj_ext metadata within unsed slab space Harry Yoo
2026-01-13 6:18 ` [PATCH V6 1/9] mm/slab: use unsigned long for orig_size to ensure proper metadata align Harry Yoo
2026-01-13 6:18 ` [PATCH V6 2/9] mm/slab: allow specifying free pointer offset when using constructor Harry Yoo
2026-01-13 6:18 ` [PATCH V6 3/9] ext4: specify the free pointer offset for ext4_inode_cache Harry Yoo
2026-01-13 6:18 ` [PATCH V6 4/9] mm/slab: abstract slabobj_ext access via new slab_obj_ext() helper Harry Yoo
2026-01-13 6:18 ` [PATCH V6 5/9] mm/slab: use stride to access slabobj_ext Harry Yoo
2026-01-13 6:18 ` [PATCH V6 6/9] mm/memcontrol,alloc_tag: handle slabobj_ext access under KASAN poison Harry Yoo
2026-01-13 6:18 ` [PATCH V6 7/9] mm/slab: save memory by allocating slabobj_ext array from leftover Harry Yoo
2026-01-13 6:18 ` [PATCH V6 8/9] mm/slab: move [__]ksize and slab_ksize() to mm/slub.c Harry Yoo
2026-01-13 12:44 ` Vlastimil Babka [this message]
2026-01-13 13:05 ` Harry Yoo
2026-01-13 13:45 ` Vlastimil Babka
2026-01-13 6:18 ` [PATCH V6 9/9] mm/slab: place slabobj_ext metadata in unused space within s->size Harry Yoo
2026-01-13 12:50 ` Vlastimil Babka
2026-01-13 13:01 ` Harry Yoo
2026-01-13 13:32 ` Harry Yoo
2026-01-13 13:42 ` Vlastimil Babka
2026-01-13 14:13 ` [PATCH V6 0/9] mm/slab: reduce slab accounting memory overhead by allocating slabobj_ext metadata within unsed slab space Vlastimil Babka
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=2cdff2ed-a45d-47e9-94ef-f8ecd178bbae@suse.cz \
--to=vbabka@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=cl@gentwo.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=hao.li@linux.dev \
--cc=harry.yoo@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=tytso@mit.edu \
--cc=vincenzo.frascino@arm.com \
--cc=yeoreum.yun@arm.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