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 0/9] mm/slab: reduce slab accounting memory overhead by allocating slabobj_ext metadata within unsed slab space
Date: Tue, 13 Jan 2026 15:13:41 +0100 [thread overview]
Message-ID: <11e83aa3-0ebb-44ad-b814-a76fd244cbf1@suse.cz> (raw)
In-Reply-To: <20260113061845.159790-1-harry.yoo@oracle.com>
On 1/13/26 7:18 AM, Harry Yoo wrote:
> V5: https://lore.kernel.org/linux-mm/20260105080230.13171-1-harry.yoo@oracle.com
> V5 -> V6:
>
> - Patch 1: Added Closes: tag for related discussion (Vlastimil)
> https://lore.kernel.org/linux-mm/1372138e-5837-4634-81de-447a1ef0a5ad@suse.cz
>
> - Patch 3: Addressed Vlastimil's comments
> https://lore.kernel.org/linux-mm/e28c08e4-5048-429b-97a0-8d51e494efcd@suse.cz
>
> - Patch 4: Fixed incorrect function prototype of slab_obj_ext() on
> !CONFIG_SLAB_OBJ_EXT builds and kept pointer type in
> free_slab_obj_exts() (Hao, Vlastimil)
> https://lore.kernel.org/linux-mm/n6kyluk3nahdxytwek4ijzy4en6mc6ps7fjjgftww4ith7llom@cijm4who24w2
> https://lore.kernel.org/linux-mm/473d479c-4eae-4589-b8c2-e2a29e8e6bc1@suse.cz
>
> - Patch 7, 9: Rewrote obj_exts_in_slab() to check if the pointer is within the
> slab's range, and distinguish by stride (Vlastimil)
> https://lore.kernel.org/linux-mm/644e163d-edd9-4128-9516-0f70a25526df@suse.cz
>
> - Patch 9: Fixed potentioal memory leak due to incorrect impl. of
> obj_exts_in_object() (Vlastimil)
> https://lore.kernel.org/linux-mm/8c67dcbe-f393-4da6-8d24-f9da79c246c4@suse.cz/
>
> - Patch 9: Fixed incorrect ksize() implementation (Hao)
> https://lore.kernel.org/linux-mm/fgx3lapibabra4x7tewx55nuvxz235ruvm3agpprjbdcmt3rc6@h54ln5tfdssz
Merged to slab/for-7.0/obj_metadata and slab/for-next, thanks!
prev parent reply other threads:[~2026-01-13 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 6:18 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
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 ` Vlastimil Babka [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=11e83aa3-0ebb-44ad-b814-a76fd244cbf1@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