linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Christoph Lameter <cl@linux.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jens Axboe <axboe@kernel.dk>,
	"lee.schermerhorn@hp.com" <lee.schermerhorn@hp.com>,
	David Rientjes <rientjes@google.com>
Subject: Re: [patch v3]numa: add a sysctl to control interleave allocation granularity from each node to improve I/O performance
Date: Wed, 14 Dec 2011 10:33:47 +0800	[thread overview]
Message-ID: <1323830027.22361.401.camel@sli10-conroe> (raw)
In-Reply-To: <20111213203856.GA6312@tassilo.jf.intel.com>

On Wed, 2011-12-14 at 04:38 +0800, Andi Kleen wrote:
> On Tue, Dec 13, 2011 at 02:12:58PM -0600, Christoph Lameter wrote:
> > On Tue, 13 Dec 2011, Andi Kleen wrote:
> > 
> > > I would prefer to add a new policy (INTERLEAVE_MULTI or so) for this
> > > instead of a global sysctl, that takes the additional parameter.
> > 
> > That would require a change of all scripts and code that uses
> > MPOL_INTERLEAVE. Lets not do that.
> 
> Yes, but setting a sysctl would need the same right?
> 
> It's not clear that all workloads want this.
> 
> With a global switch only you cannot set it case by case.
That's what I want to avoid letting each apps to explicitly do it, it's
a lot of burden.
That's true only workload with heavy I/O wants this. but I don't expect
it will harm other workloads.

>> Also I don't like having more per task state. Could you compute this
>> from the address instead even for the process policy case?
>
>That sounds good.
the process policy case doesn't give an address for allocation.

Thanks,
Shaohua

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-12-14  2:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12  1:58 Shaohua Li
2011-12-13 19:06 ` Andi Kleen
2011-12-13 20:12   ` Christoph Lameter
2011-12-13 20:38     ` Andi Kleen
2011-12-14  2:33       ` Shaohua Li [this message]
2011-12-14 17:53         ` Andi Kleen
2011-12-15  1:27           ` Shaohua Li
2012-01-09  7:31             ` Shaohua Li

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=1323830027.22361.401.camel@sli10-conroe \
    --to=shaohua.li@intel.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=cl@linux.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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