mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>, Robin Jarry <rjarry@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H.Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Joe Mario <jmario@redhat.com>
Subject: Re: [PATCH 0/5] x86/speculation: Disable IBRS when idle
Date: Sun, 18 Jun 2023 21:18:41 -0400	[thread overview]
Message-ID: <55219f3b-992d-ccc3-ba29-7bf33465b5cc@redhat.com> (raw)
In-Reply-To: <20230617122115.GA1830050@hirez.programming.kicks-ass.net>

On 6/17/23 08:21, Peter Zijlstra wrote:
> On Fri, Jun 16, 2023 at 10:14:52PM +0200, Robin Jarry wrote:
>> Waiman Long, Jun 16, 2023 at 21:59:
>>> For Intel processors that need to turn on IBRS to protect against
>>> Spectre v2 and Retbleed, the IBRS bit in the SPEC_CTRL MSR affects
>>> the performance of the whole core even if only one thread is turning
>>> it on when running in the kernel. For user space heavy applications,
>>> the performance impact of occasionally turning IBRS on during syscalls
>>> shouldn't be significant. Unfortunately, that is not the case when the
>>> sibling thread is idling in the kernel. In that case, the performance
>>> impact can be significant.
>>>
>>> When DPDK is running on an isolated CPU thread processing network packets
>>> in user space while its sibling thread is idle. The performance of the
>>> busy DPDK thread with IBRS on and off in the sibling idle thread are:
>>>
>>>                                  IBRS on               IBRS off
>>>                                  -------               --------
>>>    packets/second:                  7.8M                  10.4M
>>>    avg tsc cycles/packet:         282.26                 209.86
>>>
>>> This is a 25% performance degradation. The test system is a Intel Xeon
>>> 4114 CPU @ 2.20GHz.
>>>
>>> This patch series turns off IBRS when in various idle mode to eliminate
>>> the performance impact of the idling thread on its busy sibling thread.
>> Hi Longman,
>>
>> thanks a lot for the quick turnaround on this issue.
>>
>> Tested-by: Robin Jarry <rjarry@redhat.com>
> I can't see the patches -- they didn't arrive in my mailbox nor can I
> find them in the archive, in fact this here mail is the only evidence
> they exist at all.

I got a rebound message from your mail server about incorrect message 
format. It is probably caused by some problem in my end.


> However, did you all see intel_idle_ibrs() and how that is selected for
> C6 and up?
>
> What exactly isn't working there?

We were testing on the RHEL9.2 kernel which doesn't have your 
intel_idle_ibrs() patch yet. My preliminary testing does indicate your 
patch will likely work. I will ask Jerry to test a newer RHEL9.3 kernel 
with the intel_idle_ibrs() patch to see if it helps.

> Also, instead of investing more in this IBRS trainwreck, did you all try
> call-depth-stuffing ?

Yes, we are planning to backport your call-depth-stuffing code, but I 
believe there is still some issue outstanding that you need to address. 
So we need a solution to work around this issue in the mean time.

Cheers,
Longman


  parent reply	other threads:[~2023-06-19  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230616200003.745742-1-longman@redhat.com>
2023-06-16 20:14 ` Robin Jarry
2023-06-17 12:21   ` Peter Zijlstra
2023-06-17 16:13     ` Robin Jarry
2023-06-19  1:18     ` Waiman Long [this message]
2023-06-19  3:25       ` Waiman Long
2023-06-19  8:47         ` Peter Zijlstra

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=55219f3b-992d-ccc3-ba29-7bf33465b5cc@redhat.com \
    --to=longman@redhat.com \
    --cc=bp@alien8.de \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hpa@zytor.com \
    --cc=jmario@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=rjarry@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --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

all inboxes | Powered by JetHome®