Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.garry@linux.dev>
Cc: Christoph Hellwig <hch@lst.de>,
	kbusch@kernel.org, ahuang12@lenovo.com, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, sunjw10@lenovo.com,
	iommu@lists.linux.dev
Subject: Re: [PATCH] Revert "nvme-pci: clamp max_hw_sectors based on DMA optimized limitation"
Date: Thu, 8 Oct 2026 14:37:24 +0200	[thread overview]
Message-ID: <20261008123724.GA22096@lst.de> (raw)
In-Reply-To: <8cf8a8ea-c9c9-434b-aec6-e361280a88a4@linux.dev>

On Thu, Oct 08, 2026 at 08:36:54AM +0100, John Garry wrote:
> On 10/6/26 13:02, Christoph Hellwig wrote:
>> This turns down to cause up to 15% performance regressions on standard
>> large transfer workloads.  Revert it and hope the IOVA allocator can
>> eventually be fixed to remove the need for the original workaround.
>>
>> This reverts commit 3710e2b056cb92ad816e4d79fa54a6a5b6ad8cbd.
>>
>
> What was the block size and conditions for the original issue? The commit 
> just mentions that mdts=10 and we get a 4096KB max HW sectors.

Good question.  The original submitter and reporter are on Cc.



  reply	other threads:[~2026-10-08 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 12:02 [PATCH] Revert "nvme-pci: clamp max_hw_sectors based on DMA optimized limitation" Christoph Hellwig
2026-10-08  7:36 ` John Garry
2026-10-08 12:37   ` Christoph Hellwig [this message]
2026-10-09  9:11     ` [External] " Adrian Huang12
2026-10-09 15:37       ` Keith Busch
2026-10-12  8:42       ` John Garry
2026-10-12 12:17         ` Christoph Hellwig
2026-10-12 14:39           ` John Garry

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=20261008123724.GA22096@lst.de \
    --to=hch@lst.de \
    --cc=ahuang12@lenovo.com \
    --cc=iommu@lists.linux.dev \
    --cc=john.garry@linux.dev \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=sunjw10@lenovo.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