From: Bart Van Assche <bvanassche@acm.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Jaegeuk Kim <jaegeuk@kernel.org>,
Avri Altman <avri.altman@wdc.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH v4 2/7] block: Support configuring limits below the page size
Date: Mon, 6 Feb 2023 16:31:58 -0800 [thread overview]
Message-ID: <bee64ad1-a465-123e-4208-013e7dd69e04@acm.org> (raw)
In-Reply-To: <Y+GZFoHiUOQeq25d@bombadil.infradead.org>
On 2/6/23 16:19, Luis Chamberlain wrote:
> But I'm trying to do a careful review here.
That's appreciated :-)
> The commit log did not describe what *does* happen in these situations today,
> and you seem to now be suggesting in the worst case corruption can happen.
> That changes the patch context quite a bit!
>
> My question above still stands though, how many block drivers have a max
> hw sector smaller than the equivalent PAGE_SIZE. If you make your
> change, even if it fixes some new use case where corruption is seen, can
> it regress some old use cases for some old controllers?
The blk_queue_max_hw_sectors() change has been requested by a
contributor to the MMC driver (I'm not familiar with the MMC driver).
I'm not aware of any storage controllers for which the maximum segment
size is below 4 KiB.
For some storage controllers, e.g. the UFS Exynos controller, the
maximum supported segment size is 4 KiB. This patch series makes such
storage controllers compatible with larger page sizes, e.g. 16 KiB.
Does this answer your question?
Thanks,
Bart.
next prev parent reply other threads:[~2023-02-07 0:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 21:26 [PATCH v4 0/7] Add support for limits below the page size Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 1/7] block: Introduce blk_mq_debugfs_init() Bart Van Assche
2023-02-01 20:58 ` Luis Chamberlain
2023-02-01 21:23 ` Luis Chamberlain
2023-02-01 22:01 ` Bart Van Assche
2023-02-01 23:59 ` Luis Chamberlain
2023-02-02 1:06 ` Bart Van Assche
2023-02-06 16:03 ` Luis Chamberlain
2023-02-06 21:11 ` Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 2/7] block: Support configuring limits below the page size Bart Van Assche
2023-02-01 23:50 ` Luis Chamberlain
2023-02-07 0:02 ` Bart Van Assche
2023-02-07 0:19 ` Luis Chamberlain
2023-02-07 0:31 ` Bart Van Assche [this message]
2023-02-07 2:08 ` Luis Chamberlain
2023-02-07 18:26 ` Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 3/7] block: Support submitting passthrough requests with small segments Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 4/7] block: Add support for filesystem requests and " Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 5/7] block: Add support for small segments in blk_rq_map_user_iov() Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 6/7] scsi_debug: Support configuring the maximum segment size Bart Van Assche
2023-01-30 21:26 ` [PATCH v4 7/7] null_blk: " Bart Van Assche
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=bee64ad1-a465-123e-4208-013e7dd69e04@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=p.raghav@samsung.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;
as well as URLs for NNTP newsgroup(s).