linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: John Garry <john.garry@huawei.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: Fri, 12 Aug 2022 11:27:20 -0700	[thread overview]
Message-ID: <840a5f98-a53c-ce08-2833-f41d8c9a015b@opensource.wdc.com> (raw)
In-Reply-To: <fd2b1dbe-8482-cb89-2568-4909db1239b0@huawei.com>

On 2022/08/12 10:17, John Garry wrote:
> On 12/08/2022 16:41, Damien Le Moal wrote:
>>>> we noticed the commit is already in mainline now, and in our tests, there is
>>>> still similar regression and also on other platforms.
>>>> could you guide us how to check "which host driver is being used for this
>>>> test"? hope to supply some useful information.
>>>>
>>> For me, a complete kernel log may help.
>> I had a look yesterday with my test rig. I did not see any difference in the
>> default max_sectors_kb values for various drives between 5.18 and 5.19 (current
>> linus tree). The test machine has 2 AHCI adapters: Intel and Marvell. Both use
>> the regular AHCI driver. I have another rig with different ATA adapters but it
>> is powered down and I am traveling... So cannot test that right now.
>>
> 
> FWIW, on QEMU I get a difference for IDE disk for ata_piix host.
> 
> 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 ? How was this working before
without applying the swiotlb limit ?

> 
> thanks,
> John
> 
> [    1.497233] ata7: found unknown device (class 0)
> [    1.498341] ata7.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
> [    1.499030] ata7.00: 209716 sectors, multi 16: LBA48
> [    1.623795] ata2: SATA link down (SStatus 0 SControl 300)
> [    1.624633] ata1: SATA link down (SStatus 0 SControl 300)
> [    1.633395] ata6: SATA link down (SStatus 0 SControl 300)
> [    1.634200] ata5: SATA link down (SStatus 0 SControl 300)
> [    1.635094] ata4: SATA link down (SStatus 0 SControl 300)
> [    1.635887] ata3: SATA link down (SStatus 0 SControl 300)
> [    1.636748] scsi 6:0:0:0: Direct-Access     ATA      QEMU HARDDISK 
>   2.5+ PQ: 0 ANSI: 5
> [    1.641298] sd 6:0:0:0: [sda] 209716 512-byte logical blocks: (107 
> MB/102 MiB)
> [    1.642188] sd 6:0:0:0: [sda] Write Protect is off
> [    1.642770] sd 6:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [    1.642783] sd 6:0:0:0: [sda] Write cache: enabled, read cache: 
> enabled, doesn't support DPO or FUA
> [    1.644149] sd 6:0:0:0: [sda] Preferred minimum I/O size 512 bytes
> [    1.645142] sd 6:0:0:0: Attached scsi generic sg0 type 0
> [    1.655145] sd 6:0:0:0: [sda] Attached SCSI disk


-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2022-08-12 18:27 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 [this message]
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=840a5f98-a53c-ce08-2833-f41d8c9a015b@opensource.wdc.com \
    --to=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=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