From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Mike Snitzer <snitzer@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block updates for 6.9-rc1
Date: Tue, 12 Mar 2024 10:39:13 -0600 [thread overview]
Message-ID: <ZfCFMc0cNHvIB0Jz@kbusch-mbp.mynextlight.net> (raw)
In-Reply-To: <9b957380-42c7-42d8-a95e-88ac083e3ffe@kernel.dk>
On Mon, Mar 11, 2024 at 07:37:06PM -0600, Jens Axboe wrote:
> Summary is that this is obviously a pretty normal drive, and has the
> 128K transfer limit that's common there. So doesn't really explain
> anything in that regard. The segment size is also a bit odd at 33.
That's "max_segments" at 33, not segment size. Max payload is 128k,
divide by 4k nvme page size = 32 nvme pages. +1 to allow a first segment
offset, so 33 max segments for this device.
next prev parent reply other threads:[~2024-03-12 16:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 20:30 [GIT PULL] Block updates for 6.9-rc1 Jens Axboe
2024-03-11 19:43 ` pr-tracker-bot
2024-03-11 23:50 ` Johannes Weiner
2024-03-11 23:53 ` Jens Axboe
2024-03-11 23:58 ` Linus Torvalds
2024-03-12 0:02 ` Jens Axboe
2024-03-12 0:21 ` Linus Torvalds
2024-03-12 0:28 ` Mike Snitzer
2024-03-12 1:03 ` Jens Axboe
2024-03-12 1:09 ` Christoph Hellwig
2024-03-12 1:17 ` Jens Axboe
2024-03-12 1:20 ` Linus Torvalds
2024-03-12 1:23 ` Jens Axboe
2024-03-12 1:28 ` Linus Torvalds
2024-03-12 1:37 ` Jens Axboe
2024-03-12 16:39 ` Keith Busch [this message]
2024-03-12 11:53 ` Christoph Hellwig
2024-03-12 15:25 ` Jens Axboe
2024-03-12 11:52 ` Christoph Hellwig
2024-03-12 15:22 ` Mike Snitzer
2024-03-12 16:28 ` Keith Busch
2024-03-12 21:10 ` Christoph Hellwig
2024-03-12 22:22 ` Mike Snitzer
2024-03-12 22:30 ` Christoph Hellwig
2024-03-12 22:50 ` Mike Snitzer
2024-03-12 22:58 ` Christoph Hellwig
2024-04-11 20:15 ` [PATCH for-6.10 0/2] dm: use late bio-splitting and queue_limits_set Mike Snitzer
2024-04-11 20:15 ` [PATCH for-6.10 1/2] dm-crypt: stop constraining max_segment_size to PAGE_SIZE Mike Snitzer
2024-04-12 6:11 ` Christoph Hellwig
2024-04-15 14:08 ` Mikulas Patocka
2024-04-23 7:32 ` Ming Lei
2024-04-11 20:15 ` [PATCH for-6.10 2/2] dm: use queue_limits_set Mike Snitzer
2024-04-23 7:33 ` Ming Lei
2024-03-13 13:11 ` [GIT PULL] Block updates for 6.9-rc1 Ming Lei
2024-03-12 1:01 ` Jens Axboe
2024-03-12 0:25 ` Mike Snitzer
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=ZfCFMc0cNHvIB0Jz@kbusch-mbp.mynextlight.net \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=torvalds@linux-foundation.org \
/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