From: Hugh Dickins <hughd@google.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
Christoph Lameter <cl@linux.com>,
daniel.m.jordan@oracle.com,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
aaron.lu@intel.com, alex.kogan@oracle.com,
Andrew Morton <akpm@linux-foundation.org>,
boqun.feng@gmail.com, brouer@redhat.com,
Davidlohr Bueso <dave@stgolabs.net>,
dave.dice@oracle.com, dhaval.giani@oracle.com,
ktkhai@virtuozzo.com, Laurent Dufour <ldufour@linux.vnet.ibm.com>,
Pavel.Tatashin@microsoft.com,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
shady.issa@oracle.com, tariqt@mellanox.com,
Thomas Gleixner <tglx@linutronix.de>,
Tim Chen <tim.c.chen@intel.com>, Vlastimil Babka <vbabka@suse.cz>,
longman@redhat.com, Yang Shi <yang.shi@linux.alibaba.com>,
shy828301@gmail.com, subhra.mazumdar@oracle.com,
Steven Sistare <steven.sistare@oracle.com>,
Jonathan Adams <jwadams@google.com>,
Ashwin Chaugule <ashwinch@google.com>,
Salman Qazi <sqazi@google.com>,
Shakeel Butt <shakeelb@google.com>,
Michel Lespinasse <walken@google.com>,
David Rientjes <rientjes@google.com>,
Junaid Shahid <junaids@google.com>,
Neha Agarwal <nehaagarwal@google.com>,
Greg Thelen <gthelen@google.com>
Subject: Re: Plumbers 2018 - Performance and Scalability Microconference
Date: Thu, 6 Sep 2018 17:52:53 -0700 [thread overview]
Message-ID: <CANsGZ6bW0vJcRpnfAesH-9_9vnrrvMHYH-UjH50zqLtA4WALyg@mail.gmail.com> (raw)
In-Reply-To: <bd6f6f8b-4880-6c20-62f5-bb6ca3b5e6f7@oracle.com>
On Thu, Sep 6, 2018 at 2:36 PM Mike Kravetz <mike.kravetz@oracle.com> wrote:
>
> On 09/05/2018 06:58 PM, Huang, Ying wrote:
> > Hi, Christopher,
> >
> > Christopher Lameter <cl@linux.com> writes:
> >
> >> On Tue, 4 Sep 2018, Daniel Jordan wrote:
> >>
> >>> - Promoting huge page usage: With memory sizes becoming ever larger, huge
> >>> pages are becoming more and more important to reduce TLB misses and the
> >>> overhead of memory management itself--that is, to make the system scalable
> >>> with the memory size. But there are still some remaining gaps that prevent
> >>> huge pages from being deployed in some situations, such as huge page
> >>> allocation latency and memory fragmentation.
> >>
> >> You forgot the major issue that huge pages in the page cache are not
> >> supported and thus we have performance issues with fast NVME drives that
> >> are now able to do 3Gbytes per sec that are only possible to reach with
> >> directio and huge pages.
> >
> > Yes. That is an important gap for huge page. Although we have huge
> > page cache support for tmpfs, we lacks that for normal file systems.
> >
> >> IMHO the huge page issue is just the reflection of a certain hardware
> >> manufacturer inflicting pain for over a decade on its poor users by not
> >> supporting larger base page sizes than 4k. No such workarounds needed on
> >> platforms that support large sizes. Things just zoom along without
> >> contortions necessary to deal with huge pages etc.
> >>
> >> Can we come up with a 2M base page VM or something? We have possible
> >> memory sizes of a couple TB now. That should give us a million or so 2M
> >> pages to work with.
> >
> > That sounds a good idea. Don't know whether someone has tried this.
>
> IIRC, Hugh Dickins and some others at Google tried going down this path.
> There was a brief discussion at LSF/MM. It is something I too would like
> to explore in my spare time.
Almost: I never tried that path myself, but mentioned that Greg Thelen had.
Hugh
next prev parent reply other threads:[~2018-09-07 0:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 21:28 Daniel Jordan
2018-09-05 6:38 ` Mike Rapoport
2018-09-05 19:51 ` Pasha Tatashin
2018-09-06 5:49 ` Mike Rapoport
2018-09-05 15:10 ` Christopher Lameter
2018-09-05 16:17 ` Laurent Dufour
2018-09-05 17:11 ` Christopher Lameter
2018-09-05 23:01 ` Thomas Gleixner
2018-09-06 7:45 ` Laurent Dufour
2018-09-06 1:58 ` Huang, Ying
2018-09-06 14:41 ` Christopher Lameter
2018-09-07 2:17 ` Huang, Ying
2018-09-06 21:36 ` Mike Kravetz
2018-09-07 0:52 ` Hugh Dickins [this message]
2018-09-08 4:13 ` John Hubbard
2018-09-10 17:09 ` Waiman Long
2018-09-10 17:20 ` Davidlohr Bueso
2018-09-10 17:34 ` John Hubbard
2018-09-11 0:29 ` Daniel Jordan
2018-09-11 13:52 ` Waiman Long
2018-09-11 0:38 ` Daniel Jordan
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=CANsGZ6bW0vJcRpnfAesH-9_9vnrrvMHYH-UjH50zqLtA4WALyg@mail.gmail.com \
--to=hughd@google.com \
--cc=Pavel.Tatashin@microsoft.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex.kogan@oracle.com \
--cc=ashwinch@google.com \
--cc=boqun.feng@gmail.com \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.dice@oracle.com \
--cc=dave@stgolabs.net \
--cc=dhaval.giani@oracle.com \
--cc=gthelen@google.com \
--cc=junaids@google.com \
--cc=jwadams@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mike.kravetz@oracle.com \
--cc=nehaagarwal@google.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rientjes@google.com \
--cc=shady.issa@oracle.com \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=sqazi@google.com \
--cc=steven.sistare@oracle.com \
--cc=subhra.mazumdar@oracle.com \
--cc=tariqt@mellanox.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.com \
--cc=vbabka@suse.cz \
--cc=walken@google.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@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