From: John Garry <john.garry@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Oliver Sang <oliver.sang@intel.com>
Cc: 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: Sat, 13 Aug 2022 08:23:36 +0100 [thread overview]
Message-ID: <2b900d3b-9b52-5bc3-4ba8-24249f3c2e42@huawei.com> (raw)
In-Reply-To: <840a5f98-a53c-ce08-2833-f41d8c9a015b@opensource.wdc.com>
On 12/08/2022 19:27, Damien Le Moal wrote:
>> Interestingly ata dev max_sectors kb also gets capped from 32MB (LBA48)
>> -> 256KB due to swiotlb max mapping size. (It would be capped by shost
>> default max sectors 512KB without that swiotlb limit). I assume capping
>> due to swiotlb limit is not occuring on Oliver's machine.
> Yes, I was suspecting that we may be seeing a difference for anything that is
> not AHCI, e.g. with other drivers.
>
> But that seems to be the correct thing to do, no ?
Yes, this should be the correct thing to do.
> How was this working before
> without applying the swiotlb limit ?
>
Not sure. I would need to check the libata code for how it handles DMA
mapping errors, which I assume would occur for when we exceed the
swiotlb limit.
Having said this, from limited testing, whenever I check megaraid sas or
mpt3sas for performance, the length of request data never/rarely comes
close to max sectors. That why I am surprised with the regression which
Oliver reports.
Thanks,
John
next prev parent reply other threads:[~2022-08-13 7:23 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
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 [this message]
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=2b900d3b-9b52-5bc3-4ba8-24249f3c2e42@huawei.com \
--to=john.garry@huawei.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=hch@lst.de \
--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=oliver.sang@intel.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