From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: simon.derr@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [rfc][patch] 1/2 Additional cpuset features
Date: Thu, 23 Sep 2004 16:41:39 -0700 [thread overview]
Message-ID: <20040923164139.506d65d3.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409231238350.11694@server.home>
> Simon's 2nd patch provides a translation that we need at SGI for perfmon
> support within a cpuset. Without the virtualization some
> means in user space needs to exist to translate a virtual CPU number
> into a physical CPU number.
In my opinion, user space is exactly the right place for this translation.
Those inside SGI can see more detail of this in SGI Incident 903969.
But the jist of the matter is simple. Just as we (SGI) did with
cpumemsets and perfmon on 2.4 kernels, so should we do with cpusets and
perfmon on 2.6 kernels. And that is to perform this translation in
perfmon code. Is it only SGI's dplace that requires the cpuset-relative
numbering?
The kernel-user boundary should stick to a single, system-wide, numbering
of CPUs.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-09-23 23:49 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 [this message]
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
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=20040923164139.506d65d3.pj@sgi.com \
--to=pj@sgi.com \
--cc=christoph@lameter.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