linux-kernel - Re: Plumbers 2018 - Performance and Scalability Microconference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1809060059390.1416@nanos.tec.linutronix.de>
Date:   Thu, 6 Sep 2018 01:01:09 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Laurent Dufour <ldufour@...ux.vnet.ibm.com>
cc:     Christopher Lameter <cl@...ux.com>,
        Daniel Jordan <daniel.m.jordan@...cle.com>,
        linux-kernel@...r.kernel.org,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        Aaron Lu <aaron.lu@...el.com>, alex.kogan@...cle.com,
        akpm@...ux-foundation.org, boqun.feng@...il.com, brouer@...hat.com,
        dave@...olabs.net, dave.dice@...cle.com,
        Dhaval Giani <dhaval.giani@...cle.com>, ktkhai@...tuozzo.com,
        Pavel.Tatashin@...rosoft.com, paulmck@...ux.vnet.ibm.com,
        shady.issa@...cle.com, tariqt@...lanox.com, tim.c.chen@...el.com,
        vbabka@...e.cz, longman@...hat.com, yang.shi@...ux.alibaba.com,
        shy828301@...il.com, Huang Ying <ying.huang@...el.com>,
        subhra.mazumdar@...cle.com,
        Steven Sistare <steven.sistare@...cle.com>, jwadams@...gle.com,
        ashwinch@...gle.com, sqazi@...gle.com,
        Shakeel Butt <shakeelb@...gle.com>, walken@...gle.com,
        rientjes@...gle.com, junaids@...gle.com,
        Neha Agarwal <nehaagarwal@...gle.com>
Subject: Re: Plumbers 2018 - Performance and Scalability Microconference

On Wed, 5 Sep 2018, Laurent Dufour wrote:
> On 05/09/2018 17:10, Christopher Lameter 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.

And how exactly are you going to do any of those operations _without_
manipulating the page tables?

Thanks,

	tglx