From: David Mosberger <davidm@napali.hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com, gh@us.ibm.com,
riel@conectiva.com.br, akpm@zip.com.au,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
rohit.seth@intel.com, sunil.saxena@intel.com,
asit.k.mallick@intel.com
Subject: Re: large page patch
Date: Thu, 1 Aug 2002 23:26:07 -0700 [thread overview]
Message-ID: <15690.9727.831144.67179@napali.hpl.hp.com> (raw)
In-Reply-To: <20020801.222053.20302294.davem@redhat.com>
>>>>> On Thu, 01 Aug 2002 22:20:53 -0700 (PDT), "David S. Miller" <davem@redhat.com> said:
DaveM> From: David Mosberger <davidm@napali.hpl.hp.com> Date:
DaveM> Thu, 1 Aug 2002 22:24:05 -0700
DaveM> In my opinion the proposed large-page patch addresses a
DaveM> relatively pressing need for databases (primarily).
DaveM> Databases want large pages with IPC_SHM, how can this
DaveM> special syscal hack address that?
I believe the interface is OK in that regard. AFAIK, Oracle is happy
with it.
DaveM> It's great for experimentation, but give up syscall slots
DaveM> for this?
I'm a bit concerned about this, too. My preference would have been to
use the regular mmap() and shmat() syscalls with some
augmentation/hint as to what the preferred page size is (Simon
Winwood's OLS 2002 paper talks about some options here). I like this
because hints could be useful even with a transparent superpage
scheme.
The original Intel patch did use more of a hint-like approach (the
hint was a simple binary flag though: give me regular pages or give me
large pages), but Linus preferred a separate syscall interface, so the
Intel folks switched over to doing that.
--david
--
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-08-02 6:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 0:37 Andrew Morton
2002-08-02 0:43 ` David S. Miller
2002-08-02 1:26 ` Andrew Morton
2002-08-02 1:19 ` David S. Miller
2002-08-02 1:55 ` Rik van Riel
2002-08-02 1:50 ` David S. Miller
2002-08-02 2:29 ` Gerrit Huizenga
2002-08-02 2:23 ` David S. Miller
2002-08-02 2:53 ` Gerrit Huizenga
2002-08-02 5:24 ` David Mosberger
2002-08-02 5:20 ` David S. Miller
2002-08-02 6:26 ` David Mosberger [this message]
2002-08-02 6:33 ` Martin J. Bligh
2002-08-02 6:44 ` David Mosberger
2002-08-02 10:00 ` Marcin Dalecki
2002-08-02 7:08 ` Andrew Morton
2002-08-02 7:15 ` William Lee Irwin III
2002-08-02 8:20 ` David S. Miller
2002-08-02 9:05 ` Ryan Cumming
2002-08-02 9:06 ` David S. Miller
2002-08-02 12:52 ` Rik van Riel
2002-08-02 15:27 ` David Mosberger
2002-08-02 1:09 ` Martin J. Bligh
2002-08-02 1:36 ` Andrew Morton
2002-08-02 4:31 ` Daniel Phillips
2002-08-02 4:47 ` Andrew Morton
2002-08-02 3:47 ` William Lee Irwin III
2002-08-02 23:40 ` Chris Wedgwood
2002-08-02 1:34 Seth, Rohit
2002-08-02 19:31 Seth, Rohit
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=15690.9727.831144.67179@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@zip.com.au \
--cc=asit.k.mallick@intel.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rohit.seth@intel.com \
--cc=sunil.saxena@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