From: Gerrit Huizenga <gh@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Bill Davidsen <davidsen@tmr.com>,
Dave McCracken <dmccr@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 2.5.43-mm2] New shared page table patch
Date: Tue, 22 Oct 2002 11:45:11 -0700 [thread overview]
Message-ID: <E18441g-0001jW-00@w-gerrit2> (raw)
In-Reply-To: Your message of Tue, 22 Oct 2002 10:09:47 PDT. <3DB5865B.4462537F@digeo.com>
In message <3DB5865B.4462537F@digeo.com>, > : Andrew Morton writes:
> Rik van Riel wrote:
> >
> > ...
> > In short, we really really want shared page tables.
>
> Or large pages. I confess to being a little perplexed as to
> why we're pursuing both.
Large pages benefit the performance of large applications which
explicity take advantage of them (at least today - maybe in the
future, large pages will be automagically handed out to those that
can use them). And, as a side effect, they reduce KVA overhead.
Oh, and at the moment, they are non-pageable, e.g. permanently stuck
in memory.
On the other hand, shared page tables benefit any application that
shares data, including those that haven't been trained to roll over
and beg for large pages. Shared page tables are already showing large
space savings with at least one database.
gerrit
--
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/
next prev parent reply other threads:[~2002-10-22 18:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 23:06 Dave McCracken
2002-10-19 1:32 ` Ed Tomlinson
2002-10-19 19:17 ` Bill Davidsen
2002-10-19 19:36 ` Dave McCracken
2002-10-20 4:20 ` Eric W. Biederman
2002-10-20 6:18 ` Martin J. Bligh
2002-10-21 14:55 ` Eric W. Biederman
2002-10-21 15:21 ` Martin J. Bligh
2002-10-22 3:54 ` Eric W. Biederman
2002-10-22 5:55 ` Martin J. Bligh
2002-10-22 16:09 ` Rik van Riel
2002-10-22 16:14 ` Martin J. Bligh
2002-10-22 18:06 ` Bill Davidsen
2002-10-22 19:02 ` Martin J. Bligh
2002-10-22 19:21 ` Dave McCracken
2002-10-24 10:50 ` Bill Davidsen
2002-10-24 14:22 ` Martin J. Bligh
2002-10-24 14:38 ` Dave McCracken
2002-10-24 14:51 ` Martin J. Bligh
2002-10-25 17:31 ` Bill Davidsen
2002-10-24 10:42 ` Bill Davidsen
2002-10-22 17:19 ` Benjamin LaHaise
2002-10-22 17:36 ` Martin J. Bligh
2002-10-22 17:45 ` Benjamin LaHaise
2002-10-22 17:56 ` Andrew Morton
2002-10-22 18:01 ` Benjamin LaHaise
2002-10-22 19:03 ` Martin J. Bligh
2002-10-22 20:23 ` Alan Cox
2002-10-22 21:33 ` Gerrit Huizenga
2002-10-22 18:22 ` Alan Cox
2002-10-22 18:47 ` Gerrit Huizenga
2002-10-22 18:55 ` Benjamin LaHaise
2002-10-22 19:27 ` Gerrit Huizenga
2002-10-22 19:29 ` Benjamin LaHaise
2002-10-22 19:56 ` Arjan van de Ven
2002-10-22 14:26 ` Rik van Riel
2002-10-22 17:09 ` Andrew Morton
2002-10-22 17:15 ` Rik van Riel
2002-10-22 18:36 ` Dave McCracken
2002-10-22 18:49 ` Andrew Morton
2002-10-22 19:06 ` Gerrit Huizenga
2002-10-22 19:29 ` Dave McCracken
2002-10-22 19:11 ` Ulrich Drepper
2002-10-22 19:29 ` Gerrit Huizenga
2002-10-22 18:45 ` Gerrit Huizenga [this message]
2002-10-22 17:54 ` Bill Davidsen
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=E18441g-0001jW-00@w-gerrit2 \
--to=gh@us.ibm.com \
--cc=akpm@digeo.com \
--cc=davidsen@tmr.com \
--cc=dmccr@us.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=riel@conectiva.com.br \
/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