From: David Rientjes <rientjes@cs.washington.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Jackson <pj@sgi.com>,
linux-mm@kvack.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: Wed, 4 Oct 2006 21:50:19 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64N.0610042138580.5625@attu4.cs.washington.edu> (raw)
In-Reply-To: <20061004210711.aefaea6c.akpm@osdl.org>
On Wed, 4 Oct 2006, Andrew Morton wrote:
> We do that sort of thing all the time ;)
>
> It's sometimes OK to rely on common sense and not require benchmark results
> or in-field observations for everything.
>
> Or one can concoct artificial microbenchmarks, measure the impact and then
> use plain old brainpower to decide whether anyone is ever likely to want to
> do anything in real life which is approximately modelled by that benchmark.
>
> The latter is the case here and I'd say the answer is "yes". People might
> be impacted by this in real life.
>
Ah, it's ok to ask for benchmarks in the fake case which _nobody_ uses but
benchmarks in the real case which a lot of people use is unnecessary.
The funny thing is that it's not going to make the real case more
efficient at all if you follow real-world examples. Usually memory is
going to be found in the first zone anyway and when it's not it's going to
be found next. This is, after all, why the zone ordering has worked and
nobody has had a problem with it. (Not to mention you're clearing the
nodemask every second anyway.) I was hoping this would be evident in the
real case if you'd just run the code on your 1024 node setup. I guess
that will be realized later.
David
--
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-10-05 4:50 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
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 [this message]
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=Pine.LNX.4.64N.0610042138580.5625@attu4.cs.washington.edu \
--to=rientjes@cs.washington.edu \
--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=pj@sgi.com \
--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