From: Pekka Enberg <penberg@cs.helsinki.fi>
To: David Rientjes <rientjes@google.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] slub: default min_partial to at least highest cpus per node
Date: Tue, 07 Apr 2009 23:11:31 +0300 [thread overview]
Message-ID: <49DBB373.5050800@cs.helsinki.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.0904071302430.32321@chino.kir.corp.google.com>
Hi David,
On Tue, 7 Apr 2009, Pekka Enberg wrote:
>>> I'd be just as happy with the following, although it would require changing
>>> MIN_PARTIAL to be greater than its default of 5 if a node supports more cpus
>>> for optimal performance (the old patch did that automatically up to
>>> MAX_PARTIAL).
>> Hmm but why not move ->min_partial to struct kmem_cache_node as I suggested
>> and make sure it's adjusted properly as with nr_cpus_node()?
David Rientjes wrote:
> Sure, that's also possible except we'd lose the ability to tune
> min_partial with /sys/kernel/slab/cache/min_partial, unless it would then
> change n->min_partial for each N_NORMAL_MEMORY node. We lack an interface
> to change the per-node min_partial.
>
> If you think that's acceptable, I'd be just as satisfied with that
> approach as long as all archs have valid cpu_to_node() mappings at the
> time of CPU_UP_PREPARE.
Well, that doesn't change the current behavior, so sure, I think it's
acceptable. And if the new defaults seem reasonable enough, we can
probably get rid of the tunable altogether.
David Rientjes wrote:
> Aside: we're lacking in the documentation of these sysfs tunables such as
> remote_node_defrag_ratio to begin with, the only way to figure out what it
> does is by reading the code or making assumptions based on its name. I'd
> be happy to add some documentation but it'd be good to keep it separate
> from Documentation/vm/slub.txt.
AFAICT, the Documentation/ABI directory is the right place for this kind
of stuff.
Pekka
next prev parent reply other threads:[~2009-04-07 20:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 0:52 [patch] slub: default min_partial to at least highest cpus per node David Rientjes
2009-04-07 18:58 ` Pekka Enberg
2009-04-07 19:09 ` Pekka Enberg
2009-04-07 19:44 ` David Rientjes
2009-04-07 19:54 ` Pekka Enberg
2009-04-07 20:09 ` David Rientjes
2009-04-07 20:11 ` Pekka Enberg [this message]
2009-04-07 20:22 ` David Rientjes
2009-04-07 20:35 ` Pekka Enberg
2009-04-07 20:43 ` Christoph Lameter
2009-04-07 20:48 ` Pekka Enberg
2009-04-07 21:31 ` Christoph Lameter
2009-04-07 21:46 ` David Rientjes
2009-04-07 21:48 ` Christoph Lameter
2009-04-07 22:03 ` David Rientjes
2009-04-13 18:07 ` Christoph Lameter
2009-04-07 22:01 ` David Rientjes
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=49DBB373.5050800@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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