linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: John Garry <john.garry@huawei.com>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	<linux-ide@vger.kernel.org>, <lkp@lists.01.org>, <lkp@intel.com>,
	<ying.huang@intel.com>, <feng.tang@intel.com>,
	<zhengjun.xing@linux.intel.com>, <fengwei.yin@intel.com>
Subject: Re: [ata] 0568e61225: stress-ng.copy-file.ops_per_sec -15.0% regression
Date: Thu, 18 Aug 2022 10:06:48 +0800	[thread overview]
Message-ID: <Yv2euLFLjl8bEaeI@xsang-OptiPlex-9020> (raw)
In-Reply-To: <743867a6-b266-58e4-a8a6-542757916f0a@huawei.com>

hi John,

On Wed, Aug 17, 2022 at 03:04:06PM +0100, John Garry wrote:
> On 17/08/2022 14:51, Oliver Sang wrote:
> 
> Hi Oliver,
> 
> > > v5.19 + 0568e61225 : 512/512
> > > v5.19 + 0568e61225 + 4cbfca5f77 : 512/512
> > > v5.19: 1280/32767
> > > 
> > > They are want makes sense to me, at least.
> > > 
> > > Oliver, can you confirm this? Thanks!
> > I confirm below two:
> > v5.19 + 0568e61225 : 512/512
> > v5.19: 1280/32767 (as last already reported)
> 
> ack
> 
> > 
> > but below failed to build:
> > v5.19 + 0568e61225 + 4cbfca5f77
> > 
> > build_errors:
> >    - "drivers/scsi/scsi_transport_sas.c:242:33: error: implicit declaration of function 'dma_opt_mapping_size'; did you mean 'dma_max_mapping_size'? [-Werror=implicit-function-declaration]"
> >    - "drivers/scsi/scsi_transport_sas.c:241:24: error: 'struct Scsi_Host' has no member named 'opt_sectors'; did you mean 'max_sectors'?"
> > 
> > not sure if I understand this correctly?
> > for this, I just cherry-pick 0568e61225 upon v5.19,
> > then cherry-pick 4cbfca5f77 again.
> > so my branch looks like:
> > 
> > a11d8b97c3ecb8 v5.19 + 0568e61225 + 4cbfca5f77
> > 1b59440cf71f99 v5.19 + 0568e61225
> > 3d7cb6b04c3f31 (tag: v5.19,
> > 
> > did I do the right thing?
> 
> Sorry but I was not really interested in 4cbfca5f77 and I see where that
> build error is coming, but don't be concerned with it. However, for
> avoidance of doubt, if you have results for vanilla v6.0-rc1 then that would
> be appreciated.

for v6.0-rc1, it's still 512/512

> 
> I will also send a separate patch for testing if you don't mind.

sure! we are very glad that we could help.

> 
> thanks,
> John
> 


  reply	other threads:[~2022-08-18  2:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  8:05 kernel test robot
2022-08-08 14:52 ` Damien Le Moal
2022-08-09  9:58   ` John Garry
2022-08-09 14:16     ` John Garry
2022-08-09 14:57       ` Damien Le Moal
2022-08-10  8:33         ` John Garry
2022-08-10 13:52           ` Damien Le Moal
2022-08-09 14:55     ` Damien Le Moal
2022-08-09 15:16       ` David Laight
2022-08-10 13:57         ` Damien Le Moal
2022-08-12  5:01       ` Oliver Sang
2022-08-12 11:13         ` John Garry
2022-08-12 14:58           ` John Garry
2022-08-16  6:57             ` Oliver Sang
2022-08-16 10:35               ` John Garry
2022-08-16 15:42                 ` Damien Le Moal
2022-08-16 16:38                   ` John Garry
2022-08-16 20:02                     ` Damien Le Moal
2022-08-16 20:44                       ` John Garry
2022-08-17 15:55                         ` Damien Le Moal
2022-08-17 13:51                     ` Oliver Sang
2022-08-17 14:04                       ` John Garry
2022-08-18  2:06                         ` Oliver Sang [this message]
2022-08-18  9:28                           ` John Garry
2022-08-19  6:24                             ` Oliver Sang
2022-08-19  7:54                               ` John Garry
2022-08-20 16:36                               ` Damien Le Moal
2022-08-12 15:41           ` Damien Le Moal
2022-08-12 17:17             ` John Garry
2022-08-12 18:27               ` Damien Le Moal
2022-08-13  7:23                 ` John Garry
2022-08-16  2:52           ` 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=Yv2euLFLjl8bEaeI@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=hch@lst.de \
    --cc=john.garry@huawei.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=martin.petersen@oracle.com \
    --cc=ying.huang@intel.com \
    --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