From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-pci: derive and better document max segments limits
Date: Mon, 19 May 2025 09:23:03 +0200 [thread overview]
Message-ID: <20250519072303.GB9120@lst.de> (raw)
In-Reply-To: <aCdXBS6wrnXDQKca@kbusch-mbp>
On Fri, May 16, 2025 at 09:17:26AM -0600, Keith Busch wrote:
> If your page size is >=8k, this should change the value of NVME_MAX_SEGS
> to 256. I don't think that's a bad thing, but the commit message doesn't
> reflect that.
Indeed. I've update the commit log and pushed the changes to nvme-6.16.
next prev parent reply other threads:[~2025-05-19 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 7:21 [PATCH] nvme-pci: derive and better document max segments limits Christoph Hellwig
2025-05-16 15:17 ` Keith Busch
2025-05-19 7:23 ` Christoph Hellwig [this message]
2025-05-19 23:34 ` Chaitanya Kulkarni
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=20250519072303.GB9120@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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