From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: "David Rientjes" <rientjes@google.com>,
Lee.Schermerhorn@hp.com, mel@csn.ul.ie, ak@suse.de,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
clameter@sgi.com
Subject: Re: [RFC] bitmap relative operator for mempolicy extensions
Date: Thu, 14 Feb 2008 23:11:12 +0900 [thread overview]
Message-ID: <2f11576a0802140611h261b9df2qd13406e562f52864@mail.gmail.com> (raw)
In-Reply-To: <20080214123528.25274.84387.sendpatchset@jackhammer.engr.sgi.com>
Hi Paul,
> The following adds one more bitmap operator, with the usual
> cpumask and nodemask wrappers. This operator computes one
> bitmap relative to another. If the n-th bit in the origin
> mask is set, then the m-th bit of the destination mask will
> be set, where m is the position of the n-th set bit in the
> relative mask.
this patch is very interesting.
BTW:
Are you think this function name must be "relative" ?
I think "relative" implies ordered set.
but linux bitmap is abstraction of unordered set.
if possible, i prefer another name.
end up, bitmap_relative is map as pecial case, i think.
> This is initially to be used by the MPOL_F_RELATIVE_NODES
> facility being considered for mm/mempolicy.c.
agreed with node_relative idea.
I think this is very useful.
Thanks!
next prev parent reply other threads:[~2008-02-14 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 12:35 Paul Jackson
2008-02-14 14:11 ` KOSAKI Motohiro [this message]
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
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=2f11576a0802140611h261b9df2qd13406e562f52864@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®