linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Christoph Lameter <cl@linux.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM ATTEND] slab cache extension -- slab cache in fixed size
Date: Wed, 26 Feb 2014 15:04:54 +0800	[thread overview]
Message-ID: <530D9216.8050808@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1402251225280.30822@nuc>


On 02/26 2014 02:26 AM, Christoph Lameter wrote:
> On Tue, 25 Feb 2014, Jeff Liu wrote:
> 
>> In this case, another thing I'm hesitating about whether to export the cache_limit
>> via /proc/slabinfo by extending its tunable fields -- the per-CPU slab cache limit
>> and batchcount, as thus will change the user space interface and slabtop(1) need to
>> be modified accordingly.
> 
> Can you move the code to handle /sys/kernel/slab into mm/slab_common.c and
> then make slab use that? (Maybe a bit of a tough call but that has to be
> done at some point).

Yes, so that we can enabled those debug functions for both slab and slub, thanks for
your direction. :)

> 
> Once you got a directly with settings per slab then its trivial to add
> another field.

Indeed, that would be convenient afterwards.


Thanks,
-Jeff

--
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:[~2014-02-26  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 10:27 [LSF/MM ATTEND] slab cache extension -- slab cache in fixed size Jeff Liu
2014-01-31 15:44 ` Christoph Lameter
2014-02-25  3:33   ` Jeff Liu
2014-02-25 18:26     ` Christoph Lameter
2014-02-26  7:04       ` Jeff Liu [this message]
2014-02-26 15:02         ` 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=530D9216.8050808@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=cl@linux.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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).