From: Mike Travis <travis@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andi Kleen <ak@suse.de>, Paul Jackson <pj@sgi.com>,
David Rientjes <rientjes@google.com>,
Lee.Schermerhorn@hp.com, mel@csn.ul.ie,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC] bitmap relative operator for mempolicy extensions
Date: Thu, 14 Feb 2008 12:25:59 -0800 [thread overview]
Message-ID: <47B4A3D7.7040007@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802141206100.1041@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Thu, 14 Feb 2008, Andi Kleen wrote:
>
>> You're saying the kernel should use these relative masks internally?
>
> There is just some thoughts about this. Did not have time to look into the
> details. Mike?
There are a few places where the entire cpumask is not needed. For
example, in the area of core siblings on a node. There's a limit
to how many cores/threads can be on a node and the full 4k cpumask
is not needed. How this pertains to this new functionality I'm
not sure yet.
>
>> That means it would be impossible to run workloads that use the complete
>> machine because you couldn't represent all nodes.
>
> Not sure how they are addressing this.
next prev parent reply other threads:[~2008-02-14 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 12:35 [RFC] bitmap relative operator for mempolicy extensions Paul Jackson
2008-02-14 14:11 ` KOSAKI Motohiro
2008-02-14 16:35 ` Paul Jackson
2008-02-14 20:55 ` Ray Lee
2008-02-14 21:16 ` David Rientjes
2008-02-15 10:47 ` Paul Jackson
2008-02-15 0:24 ` KOSAKI Motohiro
2008-02-15 10:25 ` Paul Jackson
2008-02-15 10:58 ` Paul Jackson
2008-02-14 19:27 ` Christoph Lameter
2008-02-14 20:02 ` Andi Kleen
2008-02-14 20:06 ` Christoph Lameter
2008-02-14 20:25 ` Mike Travis [this message]
2008-02-14 20:30 ` Andi Kleen
2008-02-15 9:54 ` 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=47B4A3D7.7040007@sgi.com \
--to=travis@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=pj@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.