All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, clameter@sgi.com,
	manfred@colorfullife.com, mark.fasheh@oracle.com,
	alok.kataria@calsoftinc.com, kiran@scalex86.org
Subject: Re: [PATCH] slab: Don't scan cache_cache
Date: Sat, 25 Feb 2006 23:50:13 +0200	[thread overview]
Message-ID: <1140904214.11182.1.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0602240815010.20760@schroedinger.engr.sgi.com>

On Fri, 24 Feb 2006, Pekka J Enberg wrote:
> > From: Pekka Enberg <penberg@cs.helsinki.fi>
> > 
> > The cache_cache object cache is used for bootstrapping, but the cache is
> > essentially static. It is unlikely that we ever have more than one page
> > allocated for it. As SLAB_NO_REAP is gone now, fix a regression by skipping
> > cache_cache explicitly in cache_reap().

On Fri, 2006-02-24 at 08:16 -0800, Christoph Lameter wrote:
> There are other essentially static caches as well. Could we have something 
> more general?
> 
> Are you really seeing any measurable regression?

I haven't measured it but it seems obvious enough that especially for
low end boxes. I don't think something more general is required because
other static caches should use kmalloc() instead.

			Pekka


  reply	other threads:[~2006-02-25 21:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24  7:52 [PATCH] slab: Don't scan cache_cache Pekka J Enberg
2006-02-24 16:16 ` Christoph Lameter
2006-02-25 21:50   ` Pekka Enberg [this message]
2006-02-27  2:25     ` Ravikiran G Thirumalai

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=1140904214.11182.1.camel@localhost \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@osdl.org \
    --cc=alok.kataria@calsoftinc.com \
    --cc=clameter@engr.sgi.com \
    --cc=clameter@sgi.com \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mark.fasheh@oracle.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 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.