[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56ea846e-bce8-2508-e485-1dada8c39643@intel.com>
Date: Tue, 16 May 2023 07:12:34 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Rong Tao <rtoax@...mail.com>, tglx@...utronix.de
Cc: Rong Tao <rongtao@...tc.cn>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/vdso: Use non-serializing instruction rdtsc
On 5/15/23 23:52, Rong Tao wrote:
> Replacing rdtscp or 'lfence;rdtsc' with the non-serializable instruction
> rdtsc can achieve a 40% performance improvement with only a small loss of
> precision.
I think the minimum that can be done in a changelog like this is to
figure out _why_ a RDTSCP was in use. There are a ton of things that
can make the kernel go faster, but not all of them are a good idea.
I assume that the folks that wrote this had good reason for not using
plain RSTSC. What were those reasons?
Powered by blists - more mailing lists