[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4014a51d-0925-c0dc-70dc-1a465dd278e7@huawei.com>
Date: Fri, 19 Aug 2022 08:54:42 +0100
From: John Garry <john.garry@...wei.com>
To: Oliver Sang <oliver.sang@...el.com>,
Damien Le Moal <damien.lemoal@...nsource.wdc.com>
CC: Christoph Hellwig <hch@....de>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
"Linux Memory Management List" <linux-mm@...ck.org>,
<linux-ide@...r.kernel.org>, <lkp@...ts.01.org>, <lkp@...el.com>,
<ying.huang@...el.com>, <feng.tang@...el.com>,
<zhengjun.xing@...ux.intel.com>, <fengwei.yin@...el.com>
Subject: Re: [ata] 0568e61225: stress-ng.copy-file.ops_per_sec -15.0%
regression
On 19/08/2022 07:24, Oliver Sang wrote:
>> 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
Based on result below, I wonder if SAS HBAs (which use libata) should
not use default SCSI max_sectors also. Any libsas HBA driver does today,
IIRC.
>> 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
>
great, thanks
Thanks,
John
Powered by blists - more mailing lists