From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Carel Si <beibei.si@intel.com>, Jann Horn <jannh@google.com>,
Miklos Szeredi <mszeredi@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, kernel test robot <lkp@intel.com>,
fengwei.yin@intel.com, stable <stable@vger.kernel.org>
Subject: Re: [LKP] Re: [fget] 054aa8d439: will-it-scale.per_thread_ops -5.7% regression
Date: Wed, 15 Dec 2021 13:54:33 +0100 [thread overview]
Message-ID: <Ybnlic4KUznysQvl@kroah.com> (raw)
In-Reply-To: <CAHk-=whoMGTAAyah0jH+rHyAXCLnxAHu8KffrR8PrAXGhTxRdA@mail.gmail.com>
On Mon, Dec 13, 2021 at 11:44:31AM -0800, Linus Torvalds wrote:
> On Mon, Dec 13, 2021 at 10:37 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > So I'll just apply the patch. Thanks for the report and the testing
>
> Done, it's commit e386dfc56f83 ("fget: clarify and improve
> __fget_files() implementation") in my tree now.
>
> I didn't mark it as "Fixes:" or for stable, because I can't imagine
> that it matters in real life.
>
> But then it struck me that Greg has mentioned that he ends up getting
> a lot of performance regression reports for people testing stable and
> they can be distracting.
>
> So I'm adding a stable cc here just so people are aware of this as a
> "yeah, will-it-scale.poll2 performance regression has been reported,
> has a fix available if somebody cares".
Thanks, I'll keep an eye on this.
greg k-h
next prev parent reply other threads:[~2021-12-15 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 5:37 [fget] 054aa8d439: will-it-scale.per_thread_ops -5.7% regression kernel test robot
2021-12-10 18:33 ` Linus Torvalds
2021-12-10 20:29 ` Jann Horn
2021-12-10 21:25 ` Linus Torvalds
2021-12-10 21:59 ` Linus Torvalds
2021-12-10 23:29 ` Jann Horn
2021-12-11 1:01 ` Linus Torvalds
2021-12-11 1:32 ` Linus Torvalds
2021-12-13 8:31 ` [LKP] " Carel Si
2021-12-13 18:37 ` Linus Torvalds
2021-12-13 19:44 ` Linus Torvalds
2021-12-15 12:54 ` Greg KH [this message]
2021-12-13 10:57 ` Carel Si
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=Ybnlic4KUznysQvl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=beibei.si@intel.com \
--cc=fengwei.yin@intel.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).