public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: ak@suse.de, dgc@sgi.com, steiner@sgi.com, Simon.Derr@bull.net,
	linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH 01/02] cpuset memory spread slab cache filesys
Date: Wed, 1 Mar 2006 14:52:11 -0800	[thread overview]
Message-ID: <20060301145211.50ed98d2.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603011411190.31997@schroedinger.engr.sgi.com>

Well, as to what should be the default for this, enabling or not
enabling memory spreading on these inode and similar such slab caches,
I will have to leave that up to others more expert than I.

I am content to suggest that the default should reflect either the
current default (no spreading, as such was not an option until now) or
what is best for the majority of systems (whatever that is).

Probably best not to change the default, unless there is a clear
concensus that it's wrong in the majority of cases.

Whatever systems don't like the default can change it easily enough,
one way or the other.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2006-03-01 22:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27  7:02 [PATCH 01/02] cpuset memory spread slab cache filesys Paul Jackson
2006-02-27  7:02 ` [PATCH 02/02] cpuset memory spread slab cache format Paul Jackson
2006-02-27 19:34 ` [PATCH 01/02] cpuset memory spread slab cache filesys Andi Kleen
2006-02-27 20:16   ` Paul Jackson
2006-02-27 20:36     ` Christoph Lameter
2006-02-27 20:49       ` Andi Kleen
2006-02-27 20:56         ` Christoph Lameter
2006-02-27 21:02           ` Andi Kleen
2006-02-27 22:14             ` Christoph Lameter
2006-02-27 22:39               ` Andi Kleen
2006-02-27 23:13                 ` Christoph Lameter
2006-02-28  1:56                   ` Paul Jackson
2006-02-28 17:13                     ` Andi Kleen
2006-03-01 18:27                       ` Paul Jackson
2006-03-01 18:34                         ` Andi Kleen
2006-03-01 18:38                           ` Christoph Lameter
2006-03-01 18:58                           ` Paul Jackson
2006-03-01 19:21                             ` Andi Kleen
2006-03-01 20:53                               ` Paul Jackson
2006-03-01 20:59                                 ` Andi Kleen
2006-03-01 21:19                                   ` Paul Jackson
2006-03-01 21:21                                     ` Andi Kleen
2006-03-01 22:20                                       ` Christoph Lameter
2006-03-01 22:52                                         ` Paul Jackson [this message]
2006-03-02  1:57                                         ` Andi Kleen
2006-03-02 14:38                                           ` 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=20060301145211.50ed98d2.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=ak@suse.de \
    --cc=clameter@engr.sgi.com \
    --cc=clameter@sgi.com \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.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