From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: rientjes@google.com, Lee.Schermerhorn@hp.com,
linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [RFC] cpuset relative memory policies - second choice
Date: Thu, 1 Nov 2007 10:26:16 -0700 [thread overview]
Message-ID: <20071101102616.826d45a1.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711011006070.29468@schroedinger.engr.sgi.com>
Christoph wrote:
> The library interface can set flags to modify behavior.
A library such as libnuma can set them, yes, but not everyone uses
libnuma. Basically everyone uses the standard C library, glibc, which
has the system call wrappers, but these wrappers should not be setting
optional flags.
We're going around in circles here, Christoph.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2007-11-01 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 6:17 [RFC] cpuset relative memory policies - second choice Paul Jackson
2007-10-31 18:59 ` Christoph Lameter
2007-10-31 20:19 ` Paul Jackson
2007-10-31 21:05 ` Christoph Lameter
2007-11-01 4:47 ` Paul Jackson
2007-11-01 5:25 ` Christoph Lameter
2007-11-01 6:33 ` Paul Jackson
2007-11-01 8:03 ` David Rientjes
2007-11-01 13:07 ` Christoph Lameter
2007-11-01 16:06 ` Paul Jackson
2007-11-01 17:07 ` Christoph Lameter
2007-11-01 17:26 ` Paul Jackson [this message]
2007-11-01 17:38 ` Lee Schermerhorn
2007-11-01 17:44 ` Christoph Lameter
2007-11-01 19:06 ` David Rientjes
2007-11-01 19:03 ` David Rientjes
2007-11-01 19:00 ` David Rientjes
2007-11-01 18:52 ` 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=20071101102616.826d45a1.pj@sgi.com \
--to=pj@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--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