From: Ian Wienand <ianw@gelato.unsw.edu.au>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC 2/3] LVHPT - Setup LVHPT
Date: Wed, 3 May 2006 07:29:15 +1000 [thread overview]
Message-ID: <20060502212915.GA12900@cse.unsw.EDU.AU> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F066076B6@scsmsx401.amr.corp.intel.com>
On Tue, May 02, 2006 at 08:03:16AM -0700, Luck, Tony wrote:
> + help
> + The long format VHPT is an alternative hashed page table. Advantages
> + of the long format VHPT are lower memory usage when there are a large
> + number of processes in the system.
>
> Is this really true? Don't you still have all of the 3-level (or 4-level)
> tree allocated to keep the machine independent code in mm/memory.c
> happy in addition to the big block of memory that you are using on
> each cpu for the LVHPT? Where is the saving?
Yes that does seem a bit miss-leading. I guess the point was that
with short format you dedicate the top areas of your region to page
tables for each process, with long format it is static.
-i
--
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-05-02 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 15:03 [RFC 2/3] LVHPT - Setup LVHPT Luck, Tony
2006-05-02 17:30 ` Chen, Kenneth W
2006-05-03 7:49 ` Ian Wienand
2006-05-03 8:07 ` Christian Hildner
2006-05-02 21:29 ` Ian Wienand [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-04 16:58 Luck, Tony
2006-05-02 21:33 Luck, Tony
2006-05-02 5:25 [RFC 0/3] IA64 Long Format VHPT support Ian Wienand
2006-05-02 5:25 ` [RFC 2/3] LVHPT - Setup LVHPT Ian Wienand
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=20060502212915.GA12900@cse.unsw.EDU.AU \
--to=ianw@gelato.unsw.edu.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).