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: Fri, 19 Aug 2022 14:24:03 +0800 [thread overview] Message-ID: <Yv8sg3J8PLD56osY@xsang-OptiPlex-9020> (raw) In-Reply-To: <d1b1d434-059d-4d76-5fc6-092ab9ba6e16@huawei.com> On Thu, Aug 18, 2022 at 10:28:30AM +0100, John Garry wrote: > On 18/08/2022 03:06, Oliver Sang wrote: > > Hi Oliver, > > > > > 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. > > As you probably saw, I sent "[RFT PATCH] ata: libata: Set __ATA_BASE_SHT > max_sectors" for testing on top of v6.0-rc1, and I hope that then we can get > same performance as v5.19 yeah, our test confirmed your expectation: stress-ng.copy-file.ops_per_sec v5.19 - 26.85 v6.0-rc1 - 23.03 v6.0-rc1 + your patch - 26.94 > > Thanks, > John
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Sang <oliver.sang@intel.com> To: lkp@lists.01.org Subject: Re: [ata] 0568e61225: stress-ng.copy-file.ops_per_sec -15.0% regression Date: Fri, 19 Aug 2022 14:24:03 +0800 [thread overview] Message-ID: <Yv8sg3J8PLD56osY@xsang-OptiPlex-9020> (raw) In-Reply-To: <d1b1d434-059d-4d76-5fc6-092ab9ba6e16@huawei.com> [-- Attachment #1: Type: text/plain, Size: 973 bytes --] On Thu, Aug 18, 2022 at 10:28:30AM +0100, John Garry wrote: > On 18/08/2022 03:06, Oliver Sang wrote: > > Hi Oliver, > > > > > 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. > > As you probably saw, I sent "[RFT PATCH] ata: libata: Set __ATA_BASE_SHT > max_sectors" for testing on top of v6.0-rc1, and I hope that then we can get > same performance as v5.19 yeah, our test confirmed your expectation: stress-ng.copy-file.ops_per_sec v5.19 - 26.85 v6.0-rc1 - 23.03 v6.0-rc1 + your patch - 26.94 > > Thanks, > John
next prev parent reply other threads:[~2022-08-19 6:24 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-05 8:05 [ata] 0568e61225: stress-ng.copy-file.ops_per_sec -15.0% regression kernel test robot 2022-08-05 8:05 ` kernel test robot 2022-08-08 14:52 ` Damien Le Moal 2022-08-08 14:52 ` Damien Le Moal 2022-08-09 9:58 ` John Garry 2022-08-09 9:58 ` John Garry 2022-08-09 14:16 ` John Garry 2022-08-09 14:16 ` John Garry 2022-08-09 14:57 ` Damien Le Moal 2022-08-09 14:57 ` Damien Le Moal 2022-08-10 8:33 ` John Garry 2022-08-10 8:33 ` John Garry 2022-08-10 13:52 ` Damien Le Moal 2022-08-10 13:52 ` Damien Le Moal 2022-08-09 14:55 ` Damien Le Moal 2022-08-09 14:55 ` Damien Le Moal 2022-08-09 15:16 ` David Laight 2022-08-09 15:16 ` David Laight 2022-08-10 13:57 ` Damien Le Moal 2022-08-10 13:57 ` Damien Le Moal 2022-08-12 5:01 ` Oliver Sang 2022-08-12 5:01 ` Oliver Sang 2022-08-12 11:13 ` John Garry 2022-08-12 11:13 ` John Garry 2022-08-12 14:58 ` John Garry 2022-08-12 14:58 ` John Garry 2022-08-16 6:57 ` Oliver Sang 2022-08-16 6:57 ` Oliver Sang 2022-08-16 10:35 ` John Garry 2022-08-16 10:35 ` John Garry 2022-08-16 15:42 ` Damien Le Moal 2022-08-16 15:42 ` Damien Le Moal 2022-08-16 16:38 ` John Garry 2022-08-16 16:38 ` John Garry 2022-08-16 20:02 ` Damien Le Moal 2022-08-16 20:02 ` Damien Le Moal 2022-08-16 20:44 ` John Garry 2022-08-16 20:44 ` John Garry 2022-08-17 15:55 ` Damien Le Moal 2022-08-17 15:55 ` Damien Le Moal 2022-08-17 13:51 ` Oliver Sang 2022-08-17 13:51 ` Oliver Sang 2022-08-17 14:04 ` John Garry 2022-08-17 14:04 ` John Garry 2022-08-18 2:06 ` Oliver Sang 2022-08-18 2:06 ` Oliver Sang 2022-08-18 9:28 ` John Garry 2022-08-18 9:28 ` John Garry 2022-08-19 6:24 ` Oliver Sang [this message] 2022-08-19 6:24 ` Oliver Sang 2022-08-19 7:54 ` John Garry 2022-08-19 7:54 ` John Garry 2022-08-20 16:36 ` Damien Le Moal 2022-08-20 16:36 ` Damien Le Moal 2022-08-12 15:41 ` Damien Le Moal 2022-08-12 15:41 ` Damien Le Moal 2022-08-12 17:17 ` John Garry 2022-08-12 17:17 ` John Garry 2022-08-12 18:27 ` Damien Le Moal 2022-08-12 18:27 ` Damien Le Moal 2022-08-13 7:23 ` John Garry 2022-08-13 7:23 ` John Garry 2022-08-16 2:52 ` Oliver Sang 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=Yv8sg3J8PLD56osY@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.