From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Robin Holt <holt@sgi.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org
Subject: Re: ZERO_PAGE refcounting causes cache line bouncing
Date: Tue, 20 Mar 2007 13:35:58 +1100 [thread overview]
Message-ID: <45FF488E.6060707@yahoo.com.au> (raw)
In-Reply-To: <20070319120347.GB6694@lnx-holt.americas.sgi.com>
Robin Holt wrote:
> On Mon, Mar 19, 2007 at 04:56:47PM +1100, Nick Piggin wrote:
>
>>Yes, I have the patch to do it quite easily. Per-node ZERO_PAGE could be
>>another option, but that's going to cost another page flag if we wish to
>>recognise the zero page in wp faults like we do now (hmm, for some reason
>>it is OK to special case it _there_).
>
>
> Could we do a per-node ZERO_PAGE as a pointer from the node structure
> and then use a page_to_nid to get back to the node and compare the page
> to the node's zero page instead of using another page flag which would
> actually only be used on numa?
Yes, that's a nice way to do it.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2007-03-20 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 22:17 ZERO_PAGE refcounting causes cache line bouncing Christoph Lameter
2007-03-17 4:35 ` William Lee Irwin III
2007-03-19 5:56 ` Nick Piggin
2007-03-19 6:24 ` Nick Piggin
2007-03-19 6:41 ` Nick Piggin
2007-03-19 10:04 ` Nick Piggin
2007-03-19 17:06 ` Christoph Lameter
2007-03-20 2:53 ` Nick Piggin
2007-03-19 12:03 ` Robin Holt
2007-03-20 2:35 ` Nick Piggin [this message]
2007-03-19 12:46 ` William Lee Irwin III
2007-03-20 2:34 ` Nick Piggin
2007-03-19 17:04 ` Christoph Lameter
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=45FF488E.6060707@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=clameter@sgi.com \
--cc=holt@sgi.com \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.