linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rongwei Wang <rongwei.wang@linux.alibaba.com>
To: guro@fb.com
Cc: akpm@linux-foundation.org, cl@linux.com, hannes@cmpxchg.org,
	linux-kernel@vger.kernel.org, lkp@intel.com, mhocko@kernel.org,
	shakeelb@google.com, tj@kernel.org, vbabka@suse.cz,
	zhengjun.xing@linux.intel.com
Subject: Re: [LKP] Re: [mm] 10befea91b: hackbench.throughput -62.4% regression
Date: Sat, 26 Nov 2022 10:22:32 +0800	[thread overview]
Message-ID: <b8b08514-1d5c-ee21-b74f-5919d8ab5dfa@linux.alibaba.com> (raw)
In-Reply-To: <YCcp7pwzlQy15v5H@carbon.dhcp.thefacebook.com>

Hi, Roman

We also found the same regression of hackbench.throughput in our 
kernel-5.10, likes described in [1].

It seems that the mail thread in [2] doesn't show the last solution. So 
I wonder whether the upstream already has fix patch or solution can help 
us to solve this regression.

Thanks!

[1] 
https://lore.kernel.org/lkml/20210114025151.GA22932@xsang-OptiPlex-9020/.
[2] 
https://lore.kernel.org/lkml/YCcp7pwzlQy15v5H@carbon.dhcp.thefacebook.com/#R

      reply	other threads:[~2022-11-26  2:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  2:51 [mm] 10befea91b: hackbench.throughput -62.4% regression kernel test robot
2021-01-14  3:18 ` Roman Gushchin
     [not found]   ` <59b6fda7-509a-0afb-112d-46c1e73c589b@intel.com>
2021-02-03  2:49     ` [LKP] " Roman Gushchin
     [not found]       ` <8ce56447-b416-4750-eeb3-0d5bb92e007d@linux.intel.com>
2021-02-05  1:04         ` Roman Gushchin
2021-02-13  1:22         ` Roman Gushchin
2022-11-26  2:22           ` Rongwei Wang [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=b8b08514-1d5c-ee21-b74f-5919d8ab5dfa@linux.alibaba.com \
    --to=rongwei.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mhocko@kernel.org \
    --cc=shakeelb@google.com \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=zhengjun.xing@linux.intel.com \
    /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).