From: Paul Jackson <pj@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-mm@kvack.org, akpm@osdl.org, nickpiggin@yahoo.com.au,
rientjes@google.com, mbligh@google.com, rohitseth@google.com,
menage@google.com, clameter@sgi.com
Subject: Re: [TAKE] memory page_alloc zonelist caching speedup
Date: Mon, 16 Oct 2006 03:26:32 -0700 [thread overview]
Message-ID: <20061016032632.486f4235.pj@sgi.com> (raw)
In-Reply-To: <200610161134.07168.ak@suse.de>
Andi wrote:
> I think some more precise numbers would be appreciated before doing
> such changes.
Aren't there more precise numbers further down in the message to which
you were responding?
> Yes but you will add latencies for cache line bounces won't you?
> The old zone lists were completely read only. That is what worries me
> most.
There is one zonelist_cache per node, added at the end of the regular
zonelist array for each node. It will have a few words updated
typically at the rate of once per second by the CPUs sharing that node.
>From what my tests showed, and from what I'd expect, updating a few
node local words per second is not a problem.
If you have a particular architecture in mind for which the tradeoffs
in the proposed patch don't seem right, could you spell out that
architecture a bit, so we can sensibly consider whether some
refinements to this patch will suit that architecture better?
Certainly, from the numbers that I have, and by private email that
Rohit Seth has on a different architecture, this patch is neutral or a
win for the cases we considered, depending on the degree of node
locality of the memory accesses.
--
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-10-16 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 8:14 Paul Jackson
2006-10-16 9:34 ` Andi Kleen
2006-10-16 10:26 ` Paul Jackson [this message]
2006-10-16 11:25 ` Robin Holt
2006-10-16 16:58 ` Paul Jackson
2006-10-16 18:31 ` Paul Jackson
2006-11-08 10:21 ` 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=20061016032632.486f4235.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@google.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