linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-mm@kvack.org
Subject: Re: [S+Q Cleanup 6/6] slub: Move gfpflag masking out of the hotpath
Date: Tue, 17 Aug 2010 17:35:03 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1008171734150.21514@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100817211137.816192692@linux.com>

On Tue, 17 Aug 2010, Christoph Lameter wrote:

> Index: linux-2.6/mm/slub.c
> ===================================================================
> --- linux-2.6.orig/mm/slub.c	2010-08-13 10:33:09.000000000 -0500
> +++ linux-2.6/mm/slub.c	2010-08-13 10:33:13.000000000 -0500
> @@ -797,6 +797,7 @@ static void trace(struct kmem_cache *s, 
>   */
>  static inline int slab_pre_alloc_hook(struct kmem_cache *s, gfp_t flags)
>  {
> +	flags &= gfp_allowed_mask;
>  	lockdep_trace_alloc(flags);
>  	might_sleep_if(flags & __GFP_WAIT);
>  
> @@ -805,6 +806,7 @@ static inline int slab_pre_alloc_hook(st
>  
>  static inline void slab_post_alloc_hook(struct kmem_cache *s, gfp_t flags, void *object)
>  {
> +	flags &= gfp_allowed_mask;
>  	kmemcheck_slab_alloc(s, flags, object, s->objsize);
>  	kmemleak_alloc_recursive(object, s->objsize, 1, s->flags, flags);
>  }
> @@ -1678,6 +1680,7 @@ new_slab:
>  		goto load_freelist;
>  	}
>  
> +	gfpflags &= gfp_allowed_mask;
>  	if (gfpflags & __GFP_WAIT)
>  		local_irq_enable();
>  

Couldn't this include the masking of __GFP_ZERO at the beginning of 
__slab_alloc()?

> @@ -1726,8 +1729,6 @@ static __always_inline void *slab_alloc(
>  	struct kmem_cache_cpu *c;
>  	unsigned long flags;
>  
> -	gfpflags &= gfp_allowed_mask;
> -
>  	if (!slab_pre_alloc_hook(s, gfpflags))
>  		return NULL;
>  
> 
> 

--
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-18  0:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 21:11 [S+Q Cleanup 0/6] SLUB: Cleanups Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 1/6] Slub: Force no inlining of debug functions Christoph Lameter
2010-08-17 23:13   ` David Rientjes
2010-08-17 21:11 ` [S+Q Cleanup 2/6] slub: remove dynamic dma slab allocation Christoph Lameter
2010-08-17 23:35   ` David Rientjes
2010-08-18 14:46     ` Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 3/6] slub: Remove static kmem_cache_cpu array for boot Christoph Lameter
2010-08-17 23:58   ` David Rientjes
2010-08-18  6:09     ` Tejun Heo
2010-08-18 14:54     ` Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 4/6] slub: Dynamically size kmalloc cache allocations Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 5/6] slub: Extract hooks for memory checkers from hotpaths Christoph Lameter
2010-08-18  0:28   ` David Rientjes
2010-08-18 14:58     ` Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 6/6] slub: Move gfpflag masking out of the hotpath Christoph Lameter
2010-08-18  0:35   ` David Rientjes [this message]
2010-08-18 15:46     ` 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=alpine.DEB.2.00.1008171734150.21514@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    /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