From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
"Kleen, Andi" <andi.kleen@intel.com>,
"Chen, Tim C" <tim.c.chen@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: x86 TLB flushing: INVPCID vs. deferred CR3 write
Date: Wed, 6 Dec 2017 18:33:13 +0100 [thread overview]
Message-ID: <20171206173313.cnjuzn7p2wrmerui@gmail.com> (raw)
In-Reply-To: <3062e486-3539-8a1f-5724-16199420be71@intel.com>
* Dave Hansen <dave.hansen@intel.com> wrote:
> tl;dr: Kernels with pagetable isolation using INVPCID compile kernels
> 0.58% faster than using the deferred CR3 write. This tends to say that
> we should leave things as-is and keep using INVPCID, but it's far from
> definitive.
Agreed, thanks for the detailed testing!
> If folks have better ideas for a test methodology, or specific workloads or
> hardware where you want to see this tested, please speak up.
I had a look at the numbers and it all looks valid and good to me too - it's also
the intuitive result IMHO.
I suspect there might be synthetic cache-hot workloads where the +330 cycles cost
of INVPCID is higher than that of the extra TLB miss costs of a CR3 flush - but we
do know that this offset is constant, while the cost of flushing all TLBs ever
increases with the future increases of the TLB cache.
Thanks,
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-12-06 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 1:27 Dave Hansen
2017-12-06 9:37 ` Peter Zijlstra
2017-12-06 17:33 ` Ingo Molnar [this message]
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=20171206173313.cnjuzn7p2wrmerui@gmail.com \
--to=mingo@kernel.org \
--cc=andi.kleen@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tim.c.chen@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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