From: Paul Jackson <pj@sgi.com>
To: David Rientjes <rientjes@google.com>
Cc: akpm@linux-foundation.org, ak@suse.de, clameter@sgi.com,
Lee.Schermerhorn@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 4/3] cpusets: memory_spread_user interleaves over all mems_allowed
Date: Thu, 25 Oct 2007 20:19:49 -0700 [thread overview]
Message-ID: <20071025201949.9df5f10d.pj@sgi.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0710251933490.2989@chino.kir.corp.google.com>
David wrote:
> - tmp = cpuset_mems_allowed(current);
> + tmp = *newmask;
I see this as a nice little optimization, not a change in
what the code does. That is, *newmask happens to already
hold cpuset_mems_allowed(current), so can be used for such.
Is that right?
If so, nice tweak - thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2007-10-26 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 2:34 David Rientjes
2007-10-26 3:19 ` Paul Jackson [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=20071025201949.9df5f10d.pj@sgi.com \
--to=pj@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=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®