From: Roman Gushchin <guro@fb.com>
To: "Xing, Zhengjun" <zhengjun.xing@intel.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Shakeel Butt <shakeelb@google.com>,
Christoph Lameter <cl@linux.com>,
Michal Hocko <mhocko@kernel.org>, Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, <lkp@lists.01.org>,
<lkp@intel.com>
Subject: Re: [LKP] Re: [mm] 10befea91b: hackbench.throughput -62.4% regression
Date: Tue, 2 Feb 2021 18:49:51 -0800 [thread overview]
Message-ID: <20210203024951.GA1837780@carbon.DHCP.thefacebook.com> (raw)
In-Reply-To: <59b6fda7-509a-0afb-112d-46c1e73c589b@intel.com>
On Tue, Feb 02, 2021 at 04:18:27PM +0800, Xing, Zhengjun wrote:
>
>
> On 1/14/2021 11:18 AM, Roman Gushchin wrote:
> > On Thu, Jan 14, 2021 at 10:51:51AM +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed a -62.4% regression of hackbench.throughput due to commit:
> > Hi!
> >
> > Commit "mm: memcg/slab: optimize objcg stock draining" (currently only in the mm tree,
> > so no stable hash) should improve the hackbench regression.
> The commit has been merged into Linux mainline :
> 3de7d4f25a7438f09fef4e71ef111f1805cd8e7c ("mm: memcg/slab: optimize objcg
> stock draining")
> I test the regression still existed.
Hm, so in your setup it's about the same with and without this commit?
It's strange because I've received a letter stating a 45.2% improvement recently:
https://lkml.org/lkml/2021/1/27/83
Thanks!
next prev parent reply other threads:[~2021-02-03 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 2:51 kernel test robot
2021-01-14 3:18 ` Roman Gushchin
[not found] ` <59b6fda7-509a-0afb-112d-46c1e73c589b@intel.com>
2021-02-03 2:49 ` Roman Gushchin [this message]
[not found] ` <8ce56447-b416-4750-eeb3-0d5bb92e007d@linux.intel.com>
2021-02-05 1:04 ` [LKP] " Roman Gushchin
2021-02-13 1:22 ` Roman Gushchin
2022-11-26 2:22 ` Rongwei Wang
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=20210203024951.GA1837780@carbon.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mhocko@kernel.org \
--cc=oliver.sang@intel.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=zhengjun.xing@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
all inboxes | Powered by JetHome®