public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Zhou <dennis@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>, Roman Gushchin <guro@fb.com>
Cc: Pratik Sampat <psampat@linux.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"lkp@lists.01.org" <lkp@lists.01.org>,
	"lkp@intel.com" <lkp@intel.com>,
	"ying.huang@intel.com" <ying.huang@intel.com>,
	"feng.tang@intel.com" <feng.tang@intel.com>,
	"zhengjun.xing@intel.com" <zhengjun.xing@intel.com>
Subject: Re: [percpu]  ace7e70901:  aim9.sync_disk_rw.ops_per_sec -2.3% regression
Date: Fri, 7 May 2021 19:08:03 +0000	[thread overview]
Message-ID: <YJWQE8AFjyYpsLYA@google.com> (raw)
In-Reply-To: <YJV+Vn9eGfIlxDQE@carbon.dhcp.thefacebook.com>

On Fri, May 07, 2021 at 10:52:22AM -0700, Roman Gushchin wrote:
> On Fri, May 07, 2021 at 11:06:06AM +0800, Oliver Sang wrote:
> > hi Roman,
> >  
> > On Thu, May 06, 2021 at 12:54:59AM +0000, Roman Gushchin wrote:
> > > Ping
> > 
> > sorry for late.
> > 
> > the new patch makes the performance a little better but still has
> > 1.9% regression comparing to
> > f183324133 ("percpu: implement partial chunk depopulation")
> 
> Hi Oliver!
> 
> Thank you for testing it!
> 
> Btw, can you, please, confirm that the regression is coming specifically
> from ace7e70901 ("percpu: use reclaim threshold instead of running for every page")?
> I do see *some* regression in my setup, but the data is very noisy, so I'm not sure
> I can confirm it.
> 
> Thanks!

Thanks Oliver and Roman. If this is the case, I'll drop the final patch
and just merge up to f183324133 ("percpu: implement partial chunk
depopulation") into for-next as this is v5.14 anyway.

Oliver, is there a way to trigger the kernel test robot for a specific
test?

Thanks,
Dennis

  reply	other threads:[~2021-05-07 19:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  7:34 [percpu] ace7e70901: aim9.sync_disk_rw.ops_per_sec -2.3% regression kernel test robot
2021-04-30  1:25 ` Roman Gushchin
2021-05-06  0:54   ` Roman Gushchin
2021-05-07  3:06     ` Oliver Sang
2021-05-07 17:52       ` Roman Gushchin
2021-05-07 19:08         ` Dennis Zhou [this message]
2021-05-11  0:34           ` Roman Gushchin
2021-05-11  0:44             ` Dennis Zhou
2021-05-11  1:13               ` Roman Gushchin
2021-05-11  1:27                 ` Dennis Zhou
2021-05-11  2:26           ` Oliver Sang
2021-05-11  2:52             ` Dennis Zhou
2021-05-11  5:57               ` Oliver Sang
2021-05-11  2:13         ` Oliver Sang

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=YJWQE8AFjyYpsLYA@google.com \
    --to=dennis@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=guro@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=psampat@linux.ibm.com \
    --cc=ying.huang@intel.com \
    --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