mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alok Kataria <alok.kataria@calsoftinc.com>
Cc: penberg@cs.helsinki.fi, clameter@engr.sgi.com,
	manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: slab: Remove SLAB_NO_REAP option
Date: Thu, 23 Feb 2006 02:09:57 -0800	[thread overview]
Message-ID: <20060223020957.478d4cc1.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0602231502380.7798@localhost.localdomain>

Alok Kataria <alok.kataria@calsoftinc.com> wrote:
>
>  On Thu, 2006-02-23 at 14:18, Pekka Enberg wrote:
>  On 2/23/06, Alok Kataria <alok.kataria@calsoftinc.com> wrote:
>  > > There can be some caches which are not used quite often, kmem_cache 
>  > > for instance. Now from performance perspective having SLAB_NO_REAP for 
>  > > such caches is good.
>  >
>  > Yeah, kmem_cache sounds like a realistic user, but I am wondering if
>  > it makes any sense for anyone else to use it?
>  >
>  Right, thats why my question still is why do these iscsi & ocfs  cache 
>  have this flag set.

I'm sure there's no good reason.

>  If we are sure that the flag is still required, we can use the patch 
>  below.

I'm very much hoping that it is not needed.  Would prefer to just toss the
whole thing away.

What's it supposed to do anyway?  Keep wholly-unused pages hanging about in
each slab cache?  If so, it may well be a net loss - it'd be better to push
those pages back into the page allocator so they can get reused for
something else while they're possibly still in-cache.  Similarly, it's
better to fall back to the page allocator for a new slab page because
that's more likely to give us a cache-hot one.

I'm convinced, anyway ;)

  reply	other threads:[~2006-02-23 10:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  9:35 Alok Kataria
2006-02-23 10:09 ` Andrew Morton [this message]
2006-02-23 11:34   ` Pekka J Enberg
2006-02-23 17:20     ` Christoph Lameter
2006-02-23 18:36       ` Pekka Enberg
2006-02-23 18:47         ` Christoph Lameter
2006-02-23 19:17           ` Ravikiran G Thirumalai
2006-02-23 19:24             ` Christoph Lameter
2006-02-24  7:36           ` Pekka Enberg
2006-02-24 16:19             ` Christoph Lameter
2006-02-25 22:15               ` Pekka Enberg
2006-02-23 17:17   ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2006-02-22 22:34 Christoph Lameter
2006-02-23  7:46 ` Pekka Enberg
2006-02-23  7:54 ` Alok Kataria
2006-02-23  8:48   ` 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=20060223020957.478d4cc1.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alok.kataria@calsoftinc.com \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --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

Powered by JetHome