[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrXEe0shSz25oB7yk4Ee5+y3AZJ6Kt3SANeBsmLCO7StKg@mail.gmail.com>
Date: Fri, 8 Jan 2016 15:36:13 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andy Lutomirski <luto@...nel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Brian Gerst <brgerst@...il.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Oleg Nesterov <oleg@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [RFC 00/13] x86/mm: PCID and INVPCID
On Fri, Jan 8, 2016 at 3:31 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Fri, Jan 8, 2016 at 3:15 PM, Andy Lutomirski <luto@...nel.org> wrote:
>>
>> Please play around and suggest (and run?) good benchmarks. It seems
>> to save around 100ns on cross-process context switches for me.
>
> Interesting. There was reportedly (I never saw it) a test-patch to use
> pcids inside of Intel a couple of years ago, and it never got outside
> because it didn't make a difference.
I have a copy of that patch, and my code works very differently. I
only use 3 bits of PCID in this series. I could probably reduce that
to 2 with little loss. 4 or more would be a waste.
>
> Either things have changed (newer hardware with more pcids perhaps?)
> or you did a better job at it.
On my Skylake laptop, all of the PCID bits appear to have at least
some effect. Whether this means it gets hashed or whether this means
that all of the bits are real, I don't know. I'll fiddle with it on
an older machine.
--Andy
Powered by blists - more mailing lists