From: "Martin K. Petersen (Oracle)" <mkp@kernel.org>
To: Daniel Fernau <mail@danielfernau.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Shivasharan S <shivasharan.srikanteshwara@broadcom.com>,
Chandrakanth patil <chandrakanth.patil@broadcom.com>,
megaraidlinux.pdl@broadcom.com,
Thomas Lamprecht <t.lamprecht@proxmox.com>,
"James E . J . Bottomley"
<James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Damien Le Moal <dlemoal@kernel.org>,
Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Ranjan Kumar <ranjan.kumar@broadcom.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
regressions@lists.linux.dev, Lukasz Magiera <me@magik.net>,
Mira Limbeck <m.limbeck@proxmox.com>,
Mats Topstad <Mats.topstad@intility.no>,
stable@vger.kernel.org
Subject: Re: [PATCH] scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame
Date: Tue, 15 Sep 2026 22:01:22 -0400 [thread overview]
Message-ID: <yq1tsnqvtsu.fsf@mail.kernel.org> (raw)
In-Reply-To: <k5_uJWSlVpSwhVugTUyBfaq9oFVqFfpeuk_765JDKLtq_vKNO8mXI6TznKe4bX9WisARpHFxQYZ6i7W8YBT02KYaHL5d3LKSfyfCkNAh1jc=@danielfernau.com>
Daniel,
> On this hardware the cap is enough. We no longer need the
> max_sectors_kb udev workaround, and we do not see the page-boundary
> ptr_sgl fault (RAX=0x200 / 512th PRP slot) under production load.
Great, thanks for testing!
--
Martin K. Petersen
prev parent reply other threads:[~2026-09-16 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 17:24 [PATCH] scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame Thomas Lamprecht
2026-08-27 18:21 ` sashiko-bot
2026-08-28 10:21 ` Thomas Lamprecht
2026-09-03 3:10 ` Martin K. Petersen (Oracle)
2026-09-15 12:24 ` Daniel Fernau
2026-09-16 2:01 ` Martin K. Petersen (Oracle) [this message]
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=yq1tsnqvtsu.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Mats.topstad@intility.no \
--cc=axboe@kernel.dk \
--cc=chandrakanth.patil@broadcom.com \
--cc=dlemoal@kernel.org \
--cc=kashyap.desai@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.limbeck@proxmox.com \
--cc=mail@danielfernau.com \
--cc=me@magik.net \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=ranjan.kumar@broadcom.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=sumit.saxena@broadcom.com \
--cc=t.lamprecht@proxmox.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 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.