public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Robin Holt <holt@sgi.com>
Cc: anton@samba.org, christoph@lameter.com, simon.derr@bull.net,
	linux-kernel@vger.kernel.org
Subject: Re: [rfc][patch] 1/2 Additional cpuset features
Date: Fri, 24 Sep 2004 09:07:18 -0700	[thread overview]
Message-ID: <20040924090718.72bd485d.pj@sgi.com> (raw)
In-Reply-To: <20040924144147.GA14367@lnx-holt.americas.sgi.com>

Robin wrote:
> Paul, aren't we going to adjust dplace so it uses the user libraries to
> interpret the relative placement ...

Yup - either adjust dplace to accept system numbers, or adjust perfmon
to translate the system numbers that it wants to pass to dplace to
cpuset relative numbers first.  Look at the SGI internal incidents
assigned to Christoph Lameter.  I believe he's assigned this task, and
I'll bet that this is related to his response to Simon's relative cpuset
numbering patch, which started this subthread.  We've come full circle.

We're wandering off the lkml ranch here ... into vendor specific,
user space stuff.

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

      reply	other threads:[~2004-09-24 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  8:52 [rfc][patch] 1/2 Additional cpuset features Simon Derr
2004-09-11  8:08 ` Paul Jackson
2004-09-23 19:43   ` Christoph Lameter
2004-09-23 23:41     ` Paul Jackson
2004-09-24  0:06       ` Christoph Lameter
2004-09-24  1:13         ` Paul Jackson
2004-09-24  1:17         ` Anton Blanchard
2004-09-24 14:41           ` Robin Holt
2004-09-24 16:07             ` Paul Jackson [this message]

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=20040924090718.72bd485d.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=anton@samba.org \
    --cc=christoph@lameter.com \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.derr@bull.net \
    /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