linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Lameter <cl@linux.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-mm@kvack.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for August 25 (mm/slub)
Date: Wed, 25 Aug 2010 13:30:22 -0700	[thread overview]
Message-ID: <4C757D5E.1040307@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1008251405590.22117@router.home>

On 08/25/10 12:07, Christoph Lameter wrote:
> On Wed, 25 Aug 2010, Randy Dunlap wrote:
> 
>> mm/slub.c:1732: error: implicit declaration of function 'slab_pre_alloc_hook'
>> mm/slub.c:1751: error: implicit declaration of function 'slab_post_alloc_hook'
>> mm/slub.c:1881: error: implicit declaration of function 'slab_free_hook'
>> mm/slub.c:1886: error: implicit declaration of function 'slab_free_hook_irq'
> 
> Empty functions are missing if the runtime debuggability option is
> compiled
> out.
> 
> 
> Subject: slub: Add dummy functions for the !SLUB_DEBUG case
> 
> Provide the fall back functions to empty hooks if SLUB_DEBUG is not set.
> 
> Signed-off-by: Christoph Lameter <cl@linux.com>

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

Thanks.

> ---
>  mm/slub.c |   12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> Index: linux-2.6/mm/slub.c
> ===================================================================
> --- linux-2.6.orig/mm/slub.c	2010-08-25 14:02:43.000000000 -0500
> +++ linux-2.6/mm/slub.c	2010-08-25 14:04:23.000000000 -0500
> @@ -1098,6 +1098,18 @@ static inline void inc_slabs_node(struct
>  							int objects) {}
>  static inline void dec_slabs_node(struct kmem_cache *s, int node,
>  							int objects) {}
> +
> +static inline int slab_pre_alloc_hook(struct kmem_cache *s, gfp_t flags)
> +							{ return 0; }
> +
> +static inline void slab_post_alloc_hook(struct kmem_cache *s, gfp_t flags,
> +		void *object) {}
> +
> +static inline void slab_free_hook(struct kmem_cache *s, void *x) {}
> +
> +static inline void slab_free_hook_irq(struct kmem_cache *s,
> +		void *object) {}
> +
>  #endif
> 
>  /*


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

--
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>

  reply	other threads:[~2010-08-25 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100825132057.c8416bef.sfr@canb.auug.org.au>
2010-08-25 16:45 ` linux-next: Tree for August 25 (mm/slub) Randy Dunlap
2010-08-25 19:07   ` Christoph Lameter
2010-08-25 20:30     ` Randy Dunlap [this message]
2010-08-26 18:17       ` Pekka Enberg
2010-08-25 23:18     ` David Rientjes
2010-08-25 19:11   ` Christoph Lameter
2010-08-25 19:21     ` Randy Dunlap
2010-08-25 19:51       ` Christoph Lameter
2010-08-25 20:13         ` Randy Dunlap
2010-08-26 18:17           ` Pekka Enberg
2010-08-25 23:32         ` David Rientjes
2010-08-26  1:31           ` Christoph Lameter
2010-08-26 18:17             ` Pekka Enberg

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=4C757D5E.1040307@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=sfr@canb.auug.org.au \
    /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).