mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Abdul Anshad Azeez <aazees@vmware.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86\@kernel.org" <x86@kernel.org>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "rostedt\@goodmis.org" <rostedt@goodmis.org>
Subject: Re: Performance regressions in networking & storage benchmarks in Linux kernel 5.8
Date: Tue, 22 Sep 2020 13:25:53 +0200	[thread overview]
Message-ID: <87h7rqaw8u.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <BYAPR05MB4839189DFC487A1529D6734CA63B0@BYAPR05MB4839.namprd05.prod.outlook.com>

Abdul,

On Tue, Sep 22 2020 at 08:51, Abdul Anshad Azeez wrote:
> Part of VMware's performance regression testing for Linux Kernel upstream rele
> ases we compared Linux kernel 5.8 against 5.7. Our evaluation revealed perform
> ance regressions mostly in networking latency/response-time benchmarks up to 6
> 0%. Storage throughput & latency benchmarks were also up by 8%.
> In order to find the fix commit, we bisected again between 5.8 and 5.9-rc4 and
>  identified that regressions were fixed from a commit made by the same author 
> Thomas Gleixner, which unbreaks the interrupt affinity settings - "e027fffff79
> 9cdd70400c5485b1a54f482255985(x86/irq: Unbreak interrupt affinity setting)".
>
> We believe these findings would be useful to the Linux community and wanted to
>  document the same.

thanks for letting us know, but the issue is known already and the fix
has been backported to the stable kernel version 5.8.6 as of Sept. 3rd.

Please always check the latest stable version.

Thanks,

        tglx

  reply	other threads:[~2020-09-22 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  8:51 Abdul Anshad Azeez
2020-09-22 11:25 ` Thomas Gleixner [this message]
2020-09-23  7:09   ` Abdul Anshad Azeez

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=87h7rqaw8u.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=aazees@vmware.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®