From: xiongwei.song@linux.dev
To: "Suren Baghdasaryan" <surenb@google.com>, akpm@linux-foundation.org
Cc: vbabka@suse.cz, sxwjean@me.com, willy@infradead.org,
nathan@kernel.org, cl@linux.com, penberg@kernel.org,
rientjes@google.com, iamjoonsoo.kim@lge.com,
roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Suren Baghdasaryan" <surenb@google.com>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH 1/1] mm, slab: move prepare_slab_obj_exts_hook under CONFIG_MEM_ALLOC_PROFILING
Date: Fri, 12 Jul 2024 03:51:20 +0000 [thread overview]
Message-ID: <f7623c47f2ddb4ece4dc56276e214b754372cf65@linux.dev> (raw)
In-Reply-To: <20240711170216.1149695-1-surenb@google.com>
July 12, 2024 at 1:02 AM, "Suren Baghdasaryan" <surenb@google.com> wrote:
>
> The only place prepare_slab_obj_exts_hook() is currently being used is
>
> from alloc_tagging_slab_alloc_hook() when CONFIG_MEM_ALLOC_PROFILING=y.
>
> Move its definition under CONFIG_MEM_ALLOC_PROFILING to prevent unused
>
> function warning for CONFIG_SLAB_OBJ_EXT=n case.
>
> Reported-by: kernel test robot <lkp@intel.com>
>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407050845.zNONqauD-lkp@intel.com/
>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>
> Cc: Vlastimil Babka <vbabka@suse.cz>
Reviewed-by: Xiongwei Song <xiongwei.song@linux.dev>
Thanks.
>
> ---
>
> Applied over slab/for-next because of the refactoring [1] in that branch.
>
> [1] 302a3ea38aec ("mm, slab: move allocation tagging code in the alloc path into a hook")
>
> mm/slub.c | 48 +++++++++++++++++++++---------------------------
>
> 1 file changed, 21 insertions(+), 27 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
>
> index ce39544acf7c..829a1f08e8a2 100644
>
> --- a/mm/slub.c
>
> +++ b/mm/slub.c
>
> @@ -2027,6 +2027,27 @@ static inline bool need_slab_obj_ext(void)
>
> return false;
>
> }
>
>
>
> +#else /* CONFIG_SLAB_OBJ_EXT */
>
> +
>
> +static int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
>
> + gfp_t gfp, bool new_slab)
>
> +{
>
> + return 0;
>
> +}
>
> +
>
> +static inline void free_slab_obj_exts(struct slab *slab)
>
> +{
>
> +}
>
> +
>
> +static inline bool need_slab_obj_ext(void)
>
> +{
>
> + return false;
>
> +}
>
> +
>
> +#endif /* CONFIG_SLAB_OBJ_EXT */
>
> +
>
> +#ifdef CONFIG_MEM_ALLOC_PROFILING
>
> +
>
> static inline struct slabobj_ext *
>
> prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
>
> {
>
> @@ -2051,33 +2072,6 @@ prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
>
> return slab_obj_exts(slab) + obj_to_index(s, slab, p);
>
> }
>
>
>
> -#else /* CONFIG_SLAB_OBJ_EXT */
>
> -
>
> -static int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
>
> - gfp_t gfp, bool new_slab)
>
> -{
>
> - return 0;
>
> -}
>
> -
>
> -static inline void free_slab_obj_exts(struct slab *slab)
>
> -{
>
> -}
>
> -
>
> -static inline bool need_slab_obj_ext(void)
>
> -{
>
> - return false;
>
> -}
>
> -
>
> -static inline struct slabobj_ext *
>
> -prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
>
> -{
>
> - return NULL;
>
> -}
>
> -
>
> -#endif /* CONFIG_SLAB_OBJ_EXT */
>
> -
>
> -#ifdef CONFIG_MEM_ALLOC_PROFILING
>
> -
>
> static inline void
>
> alloc_tagging_slab_alloc_hook(struct kmem_cache *s, void *object, gfp_t flags)
>
> {
>
> base-commit: fe4e761669ab4d8b388fdb6e9dbe9a110eed8009
>
> --
>
> 2.45.2.993.g49e7a77208-goog
>
prev parent reply other threads:[~2024-07-12 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 17:02 [PATCH 1/1] mm, slab: move prepare_slab_obj_exts_hook under CONFIG_MEM_ALLOC_PROFILING Suren Baghdasaryan
2024-07-11 17:21 ` Vlastimil Babka
2024-07-11 18:33 ` Suren Baghdasaryan
2024-07-12 3:51 ` xiongwei.song [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=f7623c47f2ddb4ece4dc56276e214b754372cf65@linux.dev \
--to=xiongwei.song@linux.dev \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=surenb@google.com \
--cc=sxwjean@me.com \
--cc=vbabka@suse.cz \
--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.