From: Christopher Lameter <cl@linux.com>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
linux-kernel@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Aaron Lu <aaron.lu@intel.com>,
alex.kogan@oracle.com, akpm@linux-foundation.org,
boqun.feng@gmail.com, brouer@redhat.com, dave@stgolabs.net,
dave.dice@oracle.com, Dhaval Giani <dhaval.giani@oracle.com>,
ktkhai@virtuozzo.com, Pavel.Tatashin@microsoft.com,
paulmck@linux.vnet.ibm.com, shady.issa@oracle.com,
tariqt@mellanox.com, tglx@linutronix.de, tim.c.chen@intel.com,
vbabka@suse.cz, longman@redhat.com, yang.shi@linux.alibaba.com,
shy828301@gmail.com, Huang Ying <ying.huang@intel.com>,
subhra.mazumdar@oracle.com,
Steven Sistare <steven.sistare@oracle.com>,
jwadams@google.com, ashwinch@google.com, sqazi@google.com,
Shakeel Butt <shakeelb@google.com>,
walken@google.com, rientjes@google.com, junaids@google.com,
Neha Agarwal <nehaagarwal@google.com>
Subject: Re: Plumbers 2018 - Performance and Scalability Microconference
Date: Wed, 5 Sep 2018 17:11:52 +0000 [thread overview]
Message-ID: <01000165aab80769-ad7aaedf-81ae-4bbb-a602-a2aa5d49f54e-000000@email.amazonses.com> (raw)
In-Reply-To: <839e2703-1588-0873-00a7-d04810f403cf@linux.vnet.ibm.com>
On Wed, 5 Sep 2018, Laurent Dufour wrote:
> > Large page sizes also reduce contention there.
>
> That's true for the page fault path, but for process's actions manipulating the
> memory process's layout (mmap,munmap,madvise,mprotect) the impact is minimal
> unless the code has to manipulate the page tables.
Well if you compare having to operate on 4k instead of 64k then the impact
is 16xs for larger memory ranges. For smaller operations this may not be
that significant. But then I thought we were talking about large areas of
memory.
next prev parent reply other threads:[~2018-09-05 17:11 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 [this message]
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
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=01000165aab80769-ad7aaedf-81ae-4bbb-a602-a2aa5d49f54e-000000@email.amazonses.com \
--to=cl@linux.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=daniel.m.jordan@oracle.com \
--cc=dave.dice@oracle.com \
--cc=dave@stgolabs.net \
--cc=dhaval.giani@oracle.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=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