From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Nick Piggin <npiggin@suse.de>, David Chinner <dgc@sgi.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [rfc][patch] mm: scalable vmaps
Date: Mon, 18 Feb 2008 11:20:20 +0100 [thread overview]
Message-ID: <200802181120.20722.ak@suse.de> (raw)
In-Reply-To: <47B94FF7.3030200@goop.org>
> Assuming that aliased pages are relatively rare, then its OK for this
> function to be heavyweight if it can exit quickly in the non-aliased
> case (or there's some other cheap way to tell if a page has aliases).
In theory one could use a new struct page flags bit for that purpose.
On problem is though that they're already rare on 32bit
(although I still think we should just get rid of the flags->zone encoding;
then there would be plenty again)
And the other problem is that a single bit would directly only work for a single
remapping. What would you do if there are multiple remaps of the same
page though? I guess for this case you would need to put a reference
count into some separate data structure and make vunmap (or however
it's called now) search it. Could be ugly.
-Andi
--
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:[~2008-02-18 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 8:22 [rfc][patch] mm: scalable vmaps Nick Piggin
2008-02-18 9:29 ` Jeremy Fitzhardinge
2008-02-18 10:20 ` Andi Kleen [this message]
2008-02-19 1:42 ` Nick Piggin
2008-02-18 10:04 ` Andi Kleen
2008-02-19 1:46 ` Nick Piggin
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=200802181120.20722.ak@suse.de \
--to=ak@suse.de \
--cc=dgc@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).