From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: cpw@sgi.com, akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: Subject: [PATCH RESEND 1/1] cpusets/sched_domain reconciliation
Date: Fri, 23 Mar 2007 14:59:04 +1100 [thread overview]
Message-ID: <46035088.4060709@yahoo.com.au> (raw)
In-Reply-To: <20070322205038.6009989f.pj@sgi.com>
Paul Jackson wrote:
> Nick also wrote:
>
>>The problem was that Paul didn't think it followed cpus_exclusive
>>correctly, and I don't think we ever got to the point of giving it
>>a rigourous definition.
>
>
>>From Documentation/cpusets.txt:
>
> - A cpuset may be marked exclusive, which ensures that no other
> cpuset (except direct ancestors and descendents) may contain
> any overlapping CPUs or Memory Nodes.
>
> This seems like the same definition to me as you gave, and I just
> agreed to in my previous post a few minutes ago. It seems rigourous
> to me ;>.
Yeah, see my earlier reply. Naturally I was confused as to the
nature of my earlier confusion ;)
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-03-23 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:15 Cliff Wickman
2007-03-23 1:53 ` Nick Piggin
2007-03-23 3:47 ` Paul Jackson
2007-03-23 3:58 ` Nick Piggin
2007-03-23 5:16 ` Nick Piggin
2007-03-23 23:55 ` Paul Jackson
2007-03-23 3:50 ` Paul Jackson
2007-03-23 3:59 ` Nick Piggin [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=46035088.4060709@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=cpw@sgi.com \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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