From: Paul Jackson <pj@sgi.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
mbligh@aracnet.com, akpm@osdl.org, haveblue@us.ibm.com
Subject: Re: [PATCH] nodemask_t x86_64 changes [5/7]
Date: Tue, 23 Mar 2004 13:36:50 -0800 [thread overview]
Message-ID: <20040323133650.2044fd8f.pj@sgi.com> (raw)
In-Reply-To: <20040323101323.GD2045@holomorphy.com>
Yes - making the *_complement ops into two operand (dst, src) would be a
good idea, Bill. Thanks. I will likely include that in what I'm doing
now.
Meanwhile, Matthew's patch 5/7 appears broken here.
My current understanding of the complement op is that it is broken for
non-word multiple sizes. There's a good chance I'm still be confused on
this matter.
It might make sense to redo this particular bit of offline logic not by
using *_complement, but rather by looping over all nodes, and only
acting if not online, thus avoiding the *_complement() operator for now.
I have not thought through the performance implications of such a code
inversion, however.
--
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-03-23 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 23:04 [PATCH] nodemask_t x86_64 changes [5/7] Matthew Dobson
2004-03-23 7:08 ` Paul Jackson
2004-03-23 10:13 ` William Lee Irwin III
2004-03-23 21:36 ` Paul Jackson [this message]
2004-03-24 2:03 ` William Lee Irwin III
2004-03-24 4:11 ` Paul Jackson
2004-03-24 4:37 ` William Lee Irwin III
2004-03-26 5:06 ` Keith Owens
2004-03-26 7:14 ` Paul Jackson
2004-03-29 5:08 ` Keith Owens
2004-03-29 5:14 ` Paul Jackson
2004-03-29 5:38 ` William Lee Irwin III
2004-03-26 11:57 ` William Lee Irwin III
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=20040323133650.2044fd8f.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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