From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Christoph Lameter <clameter@sgi.com>, linux-mm@kvack.org
Subject: Re: ZERO_PAGE refcounting causes cache line bouncing
Date: Mon, 19 Mar 2007 05:46:30 -0700 [thread overview]
Message-ID: <20070319124630.GK8915@holomorphy.com> (raw)
In-Reply-To: <45FE261F.3030903@yahoo.com.au>
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_).
No need for a page flag. A per-node array of struct page * can be used
to check by merely indexing into it with the nid of the page's node. e.g.
struct page *get_zero_page(int nid, unsigned long addr)
{
return zero_pages[nid][(addr & SOME_ARCHDEP_MASK) >> PAGE_SHIFT];
}
/* any time we fish one out of a pte we have a uvaddr */
int is_zero_page_addr(struct page *page, unsigned long address)
{
return page == get_zero_page(page_to_nid(page), address);
}
-- wli
--
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-19 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 22:17 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
2007-03-19 12:46 ` William Lee Irwin III [this message]
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=20070319124630.GK8915@holomorphy.com \
--to=wli@holomorphy.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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