From: Vlastimil Babka <vbabka@suse.cz>
To: alexs@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Yoann Congal <yoann.congal@smile.fr>,
Masahiro Yamada <masahiroy@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH v3 1/2] mm/memcg: alignment memcg_data define condition
Date: Thu, 11 Jul 2024 10:13:08 +0200 [thread overview]
Message-ID: <42afbce8-7746-438f-ba3a-c997a2c702e5@suse.cz> (raw)
In-Reply-To: <20240710054336.190410-1-alexs@kernel.org>
On 7/10/24 7:43 AM, alexs@kernel.org wrote:
> From: "Alex Shi (Tencent)" <alexs@kernel.org>
>
> commit 21c690a349ba ("mm: introduce slabobj_ext to support slab object
> extensions") changed the folio/page->memcg_data define condition from
> MEMCG to SLAB_OBJ_EXT. And selected SLAB_OBJ_EXT for MEMCG, just for
> SLAB_MATCH(memcg_data, obj_exts), even no other relationship between them.
>
> Above action make memcg_data exposed and include SLAB_OBJ_EXT for
> !MEMCG. That's incorrect in logcial and pay on code size.
>
> As Vlastimil Babka suggested, let's add _unused_slab_obj_ext for
> SLAB_MATCH for slab.obj_exts while !MEMCG. That could resolve the match
> issue, clean up the feature logical. And decouple the SLAB_OBJ_EXT from
> MEMCG in next patch.
>
> Signed-off-by: Alex Shi (Tencent) <alexs@kernel.org>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Yoann Congal <yoann.congal@smile.fr>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: Petr Mladek <pmladek@suse.com>
> Cc: Suren Baghdasaryan <surenb@google.com>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> ---
> v1->v3: take Vlastimil's suggestion and move SLAB_OBJ_EXT/MEMCG decouple
> to 2nd patch.
> ---
> include/linux/mm_types.h | 8 ++++++--
> mm/slab.h | 4 ++++
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index ef09c4eef6d3..4ac3abc673d3 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -180,8 +180,10 @@ struct page {
> /* Usage count. *DO NOT USE DIRECTLY*. See page_ref.h */
> atomic_t _refcount;
>
> -#ifdef CONFIG_SLAB_OBJ_EXT
> +#ifdef CONFIG_MEMCG
> unsigned long memcg_data;
> +#elif defined(CONFIG_SLAB_OBJ_EXT)
> + unsigned long _unused_slab_obj_ext;
> #endif
>
> /*
> @@ -343,8 +345,10 @@ struct folio {
> };
> atomic_t _mapcount;
> atomic_t _refcount;
> -#ifdef CONFIG_SLAB_OBJ_EXT
> +#ifdef CONFIG_MEMCG
> unsigned long memcg_data;
> +#elif defined(CONFIG_SLAB_OBJ_EXT)
> + unsigned long _unused_slab_obj_ext;
> #endif
> #if defined(WANT_PAGE_VIRTUAL)
> void *virtual;
> diff --git a/mm/slab.h b/mm/slab.h
> index 3586e6183224..8ffdd4f315f8 100644
> --- a/mm/slab.h
> +++ b/mm/slab.h
> @@ -98,7 +98,11 @@ SLAB_MATCH(flags, __page_flags);
> SLAB_MATCH(compound_head, slab_cache); /* Ensure bit 0 is clear */
> SLAB_MATCH(_refcount, __page_refcount);
> #ifdef CONFIG_SLAB_OBJ_EXT
> +#ifdef CONFIG_MEMCG
> SLAB_MATCH(memcg_data, obj_exts);
> +#else
> +SLAB_MATCH(_unused_slab_obj_ext, obj_exts);
> +#endif
> #endif
Why not also #ifdef / #elif like above, instead of this nesting?
> #undef SLAB_MATCH
> static_assert(sizeof(struct slab) <= sizeof(struct page));
next prev parent reply other threads:[~2024-07-11 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 5:43 alexs
2024-07-10 5:43 ` [REF PATCH v3 2/2] mm/slab: decouple the SLAB_OBJ_EXT from MEMCG alexs
2024-07-10 6:13 ` Alex Shi
2024-07-11 8:11 ` Vlastimil Babka
2024-07-11 11:49 ` Alex Shi
2024-07-11 13:55 ` Suren Baghdasaryan
2024-07-12 4:21 ` Alex Shi
2024-07-12 7:27 ` Vlastimil Babka
2024-07-15 1:32 ` Alex Shi
2024-07-11 8:13 ` Vlastimil Babka [this message]
2024-07-11 11:51 ` [PATCH v3 1/2] mm/memcg: alignment memcg_data define condition Alex Shi
2024-07-11 14:55 ` Suren Baghdasaryan
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=42afbce8-7746-438f-ba3a-c997a2c702e5@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=penberg@kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=surenb@google.com \
--cc=yoann.congal@smile.fr \
/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
all inboxes | Powered by JetHome®