From: Paul Jackson <pj@sgi.com>
To: David Rientjes <rientjes@cs.washington.edu>
Cc: linux-mm@kvack.org, akpm@osdl.org, nickpiggin@yahoo.com.au,
ak@suse.de, mbligh@google.com, rohitseth@google.com,
menage@google.com, clameter@sgi.com
Subject: Re: [RFC] another way to speed up fake numa node page_alloc
Date: Tue, 26 Sep 2006 12:24:45 -0700 [thread overview]
Message-ID: <20060926122445.717c7c11.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0609261049260.11233@attu4.cs.washington.edu>
David wrote:
> This happens to be the case where the smaller time
> interval would be the most unfortunate.
"most unfortunate" -- that phrase sounds overly dramatic to me.
So what if the average time between zaps is 0.9 seconds instead of 1.0
seconds? More realistically, we are talking something like 0.99999
versus 1.00000 seconds, given that writing a 64 bit word on a 32 bit
arch offers only a tiny window for lost races.
Lost races that break things are unacceptable, even in tiny windows.
But lost races that just slightly nudge an already arbitrary and not
particularly fussy performance heuristic are not worth a single line
of code to avoid.
> When we free memory from a specific zone, why is it not better to use
> zone_to_nid and then zap that _node_ in the nodemask only because we are
> guaranteed that the status has changed?
It might be better. And it might not. More likely, it would be an
immeasurable difference except on custom microbenchmarks designed to
highlight this difference one way or the other.
Less code is better, unless there is better reason than this for it.
And unless I locked the bit clear, I'd still have to occassionally zap
the entire nodemask. Setting or clearing individual bits in a mask opens
a bigger critical section to races. Eventually, after loosing enough
such races, that nodemask would be suitable for donating a little bit of
entropy to the random number subsystem -- mush.
> Four people on the Cc list to this email, however, still have access to
> my script.
Perhaps you could ping them off-list, and see if they are in a position
to participate.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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>
next prev parent reply other threads:[~2006-09-26 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 9:14 Paul Jackson
2006-09-26 6:08 ` David Rientjes
2006-09-26 7:06 ` Paul Jackson
2006-09-26 18:17 ` David Rientjes
2006-09-26 19:24 ` Paul Jackson [this message]
2006-09-26 19:58 ` David Rientjes
2006-09-26 21:48 ` Paul Jackson
2006-10-02 6:18 ` Paul Jackson
2006-10-02 6:31 ` David Rientjes
2006-10-02 6:48 ` Paul Jackson
2006-10-02 7:05 ` David Rientjes
2006-10-02 8:41 ` Paul Jackson
2006-10-03 18:15 ` Paul Jackson
2006-10-03 19:37 ` David Rientjes
2006-10-04 15:45 ` Paul Jackson
2006-10-04 16:11 ` Christoph Lameter
2006-10-04 22:10 ` David Rientjes
2006-10-05 2:27 ` Paul Jackson
2006-10-05 2:37 ` David Rientjes
2006-10-05 2:53 ` Paul Jackson
2006-10-05 3:00 ` David Rientjes
2006-10-05 3:26 ` Paul Jackson
2006-10-05 3:49 ` David Rientjes
2006-10-05 4:07 ` Andrew Morton
2006-10-05 4:14 ` Paul Jackson
2006-10-05 4:50 ` David Rientjes
2006-10-05 4:53 ` Paul Jackson
2006-10-11 3:42 ` 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=20060926122445.717c7c11.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rientjes@cs.washington.edu \
--cc=rohitseth@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