On Thu, Jan 04, 2018 at 11:27:04AM +0100, Willy Tarreau wrote:
> > The post linked above has numbers with nopcid disabling pcid use, and
> > indeed, the difference is quite measurable.
>
> I'm going to re-run the tests on an Atom C2518 now, which doesn't have pcid,
> I don't even know if it's affe
On Wed, Jan 03, 2018 at 01:20:00PM -0800, Andres Freund wrote:
> On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> > I think we should start to think about an option to
> > disable this per process. We could imagine for example a prctl()
> > requiring CAP_SYS_ADMIN to disable it. This would at l
On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> > >
> > > I thought it'd be interesting to run a short benchmark to be able to
> > > estimate the impact of the PTI work
On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund 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 la
On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund 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:
On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote:
> With all the x86 pti work coming in late in the rc like this, I'm by
> now almost guaranteed to do an rc8 this release, not because there are
> any known problems, but simply because of the timing of the patches.
>
> Go forth and test,
I though
6 matches
Mail list logo
