From: Matthias Kaehlcke <mka@chromium.org>
To: David Rientjes <rientjes@google.com>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm/slub: Only define kmalloc_large_node_hook() for NUMA systems
Date: Mon, 22 May 2017 13:56:21 -0700 [thread overview]
Message-ID: <20170522205621.GL141096@google.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1705221338100.30407@chino.kir.corp.google.com>
El Mon, May 22, 2017 at 01:39:26PM -0700 David Rientjes ha dit:
> On Fri, 19 May 2017, Matthias Kaehlcke wrote:
>
> > The function is only used when CONFIG_NUMA=y. Placing it in an #ifdef
> > block fixes the following warning when building with clang:
> >
> > mm/slub.c:1246:20: error: unused function 'kmalloc_large_node_hook'
> > [-Werror,-Wunused-function]
> >
>
> Is clang not inlining kmalloc_large_node_hook() for some reason? I don't
> think this should ever warn on gcc.
clang warns about unused static inline functions outside of header
files, in difference to gcc.
> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
>
> Acked-by: David Rientjes <rientjes@google.com>
>
> > ---
> > mm/slub.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/mm/slub.c b/mm/slub.c
> > index 57e5156f02be..66e1046435b7 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
> > @@ -1313,11 +1313,14 @@ static inline void dec_slabs_node(struct kmem_cache *s, int node,
> > * Hooks for other subsystems that check memory allocations. In a typical
> > * production configuration these hooks all should produce no code at all.
> > */
> > +
> > +#ifdef CONFIG_NUMA
> > static inline void kmalloc_large_node_hook(void *ptr, size_t size, gfp_t flags)
> > {
> > kmemleak_alloc(ptr, size, 1, flags);
> > kasan_kmalloc_large(ptr, size, flags);
> > }
> > +#endif
> >
> > static inline void kfree_hook(const void *x)
> > {
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-22 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 21:00 [PATCH 0/3] mm/slub: Fix unused function warnings Matthias Kaehlcke
2017-05-19 21:00 ` [PATCH 1/3] mm/slub: Only define kmalloc_large_node_hook() for NUMA systems Matthias Kaehlcke
2017-05-22 20:39 ` David Rientjes
2017-05-22 20:56 ` Matthias Kaehlcke [this message]
2017-05-22 21:45 ` Andrew Morton
2017-05-23 1:35 ` David Rientjes
2017-05-23 16:56 ` Matthias Kaehlcke
2017-05-23 17:12 ` Doug Anderson
2017-05-24 20:36 ` David Rientjes
2017-05-24 22:09 ` Matthias Kaehlcke
2017-05-26 17:05 ` Doug Anderson
2017-05-19 21:00 ` [PATCH 2/3] mm/slub: Mark slab_free_hook() as __maybe_unused Matthias Kaehlcke
2017-05-19 21:00 ` [PATCH 3/3] mm/slub: Put tid_to_cpu() and tid_to_event() inside #ifdef block Matthias Kaehlcke
2017-05-22 15:24 ` [PATCH 0/3] mm/slub: Fix unused function warnings Christoph Lameter
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=20170522205621.GL141096@google.com \
--to=mka@chromium.org \
--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=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).