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: <CA+55aFze2mpys1e5Yf9ekr4=S2SKFnLfnM4LHU2Y8RFJ5_rugA@mail.gmail.com>
Date:   Tue, 2 Jan 2018 13:09:13 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Andres Freund <andres@...razel.de>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 4.15-rc6

On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund <andres@...razel.de> wrote:
>
> I thought it'd be interesting to run a short benchmark to be able to
> estimate the impact of the PTI work on postgres workloads (which I work
> on). On my skylake laptop, a memory resident, OLTP workload with 16
> connections results in:

Yeah, that's actually pretty much in line with expectations.

Something around 5% performance impact of the isolation is what people
are looking at.

Obviously it depends on just exactly what you do. Some loads will
hardly be affected at all, if they just spend all their time in user
space. And if you do a lot of small system calls, you might see
double-digit slowdowns.

> This isn't a complaint, I just thought it might be useful
> information. If it helps for anything/anybody, I'm happy to run
> additional benchmarks / provide additional information.

Note that it will depend heavily on the hardware too. Older CPU's
without PCID will be impacted more by the isolation. And I think some
of the back-ports won't take advantage of PCID even on newer hardware.

              Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ