From: David Rientjes <rientjes@cs.washington.edu>
To: Paul Jackson <pj@sgi.com>
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: Wed, 4 Oct 2006 20:49:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64N.0610042036230.27222@attu3.cs.washington.edu> (raw)
In-Reply-To: <20061004202656.18830f76.pj@sgi.com>
On Wed, 4 Oct 2006, Paul Jackson wrote:
> And as to why my position changed as to whether the zonelist scans
> were ever a performance issue on real numa, I've already answered that
> question ... a couple of times. Let me know if you need me to repeat
> this answer a third time.
>
No, what I need repeated a third time is why changes are being made
without data to support it, especially to something like
get_page_from_freelist that has never been complained about on real NUMA
setups. Second, what I need repeated a third time is why changes are
being made to the real NUMA case without data to show it's a problem in
the first place. This is a scientific process where we can experiment and
then collect data and analyize it to see what went right and what went
wrong. I'm a big supporter of making changes when you have a feeling that
it will make a difference because often times the experiments will prove
that it did. But I'm not a big supporter of saying "the real NUMA case
being slow was mentioned to me in passing once, I've never witnessed it,
I can't describe how to test it, and I have nothing to compare it to, so
let's add more code because it can't make it worse."
So I really don't see what the point of debating the issue is when any
number of tests could either prove or disprove this and those tests don't
need to be run by Rohit on a fake NUMA setup. You have a NUMA setup with
1024 nodes, so let's see ANY workload IN ANY CIRCUMSTANCE where the HARD
DATA shows that it improves the case. Theory is great for discussion, but
real numbers actually make the case.
[ And when I return the Seattle from east LA and I try to squeeze a 64-bit
machine out of my school, even as a lowly undergrad, I'm looking forward
to patching your patch so that it zaps the nodemask _only_ on frees and
showing that it works better in every scenario that I can think of. ]
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 3:49 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 [this message]
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=Pine.LNX.4.64N.0610042036230.27222@attu3.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