The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: clameter@sgi.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] slab: resize the alien caches too
Date: Wed, 18 Apr 2007 06:34:55 +0200	[thread overview]
Message-ID: <46259FEF.9090300@cosmosbay.com> (raw)
In-Reply-To: <20070418004418.GA30721@linux-os.sc.intel.com>

Siddha, Suresh B a écrit :
> Christoph,
> 
> While going through the slab code, I observed that alien caches are
> not getting resized, when user changes the slab tunables. Appended patch
> tries to fix this. Please review and let me know if I missed anything.
> 
> thanks,
> suresh
> ---
> 
> Resize the alien caches too based on the slab tunables.
> 
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
> ---
> 
> diff --git a/mm/slab.c b/mm/slab.c
> index 4cbac24..e0dd9af 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -3823,6 +3823,7 @@ static int alloc_kmemlist(struct kmem_cache *cachep)
>  		l3 = cachep->nodelists[node];
>  		if (l3) {
>  			struct array_cache *shared = l3->shared;
> +			struct array_cache **alien = l3->alien;
>  
>  			spin_lock_irq(&l3->list_lock);
>  

Christoph already rejected the patch, but I have one further comment : 
l3->alien should be fetched after spin_lock_irq() of course.

It's true that the :
if (limit > 1) limit = 12;
from alloc_alien_cache() is quite disturbing and could be cleaned up.



      parent reply	other threads:[~2007-04-18  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18  0:44 [patch] slab: resize the alien caches too Siddha, Suresh B
2007-04-18  0:48 ` Christoph Lameter
2007-04-18  1:14   ` Siddha, Suresh B
2007-04-18  4:34 ` Eric Dumazet [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=46259FEF.9090300@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.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