From: Christoph Lameter <clameter@engr.sgi.com>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, manfred@colorfullife.com,
Alok Kataria <alokk@calsoftinc.com>
Subject: Re: [patch 1/3] mm: NUMA slab -- add alien cache drain statistics
Date: Tue, 29 Nov 2005 09:57:58 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511290954010.14722@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20051129085049.GA3573@localhost.localdomain>
On Tue, 29 Nov 2005, Ravikiran G Thirumalai wrote:
> NUMA slab allocator frees remote objects to a local alien cache.
> But if the local alien cache is full, the alien cache
> is drained directly to the remote node.
>
> This patch adds a statistics counter which is incremented everytime the
> local alien cache is full and we have to drain it to the remote nodes list3.
>
> This will be useful when we can dynamically tune the alien cache limit.
> Currently, the alien cache limit is fixed at 12.
It may be best to first enable the basic manual tuning. See
slabinfo_write.
How would you propose to determine the length?
--
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>
next prev parent reply other threads:[~2005-11-29 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 8:50 Ravikiran G Thirumalai
2005-11-29 8:53 ` [patch 2/3] mm: NUMA slab -- node local memory for off slab slab descriptors Ravikiran G Thirumalai
2005-11-29 17:48 ` Christoph Lameter
2005-11-29 8:54 ` [patch 3/3] mm: NUMA slab -- minor optimizations Ravikiran G Thirumalai
2005-11-29 17:53 ` Christoph Lameter
2005-12-26 23:42 ` Manfred Spraul
2005-12-27 20:35 ` Christoph Lameter
2005-11-29 9:25 ` [patch 1/3] mm: NUMA slab -- add alien cache drain statistics Andrew Morton
2005-11-29 17:57 ` Christoph Lameter [this message]
2005-11-29 18:49 ` 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=Pine.LNX.4.62.0511290954010.14722@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=alokk@calsoftinc.com \
--cc=kiran@scalex86.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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