From: Arjan van de Ven <arjan@infradead.org>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Hugh Dickins <hugh@veritas.com>,
Dave McCracken <dmccr@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 1/1] Implement shared page tables
Date: Wed, 31 Aug 2005 16:41:57 +0200 [thread overview]
Message-ID: <1125499318.3213.18.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <16640000.1125498711@[10.10.2.4]>
> > Which is indeed a further disincentive against shared page tables.
>
> Or shared pagetables a disincentive to randomizing the mmap space ;-)
> They're incompatible, but you could be left to choose one or the other
> via config option.
>
> 3% on "a certain industry-standard database benchmark" (cough) is huge,
> and we expect the benefit for PPC64 will be larger as we can share the
> underlying hardware PTEs without TLB flushing as well.
>
surely the benchmark people know that the database in question always
mmaps the shared area at the address where the first one started it?
(if not, could make it so ;)
--
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:[~2005-08-31 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 22:13 Dave McCracken
2005-08-31 11:44 ` Hugh Dickins
2005-08-31 11:51 ` Arjan van de Ven
2005-08-31 13:42 ` Hugh Dickins
2005-08-31 14:31 ` Martin J. Bligh
2005-08-31 14:41 ` Arjan van de Ven [this message]
2005-08-31 15:06 ` Hugh Dickins
2005-08-31 15:39 ` Martin J. Bligh
2005-08-31 16:40 ` Dave McCracken
2005-09-02 1:58 ` Chen, Kenneth W
2005-09-02 16:40 ` Dave McCracken
2005-09-02 4:26 ` Chen, Kenneth W
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=1125499318.3213.18.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=dmccr@us.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
/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