From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Luis Chamberlain <mcgrof@kernel.org>,
Sandeep Dhavale <dhavale@google.com>,
Juan Yescas <jyescas@google.com>,
Chaitanya Kulkarni <kch@nvidia.com>,
Ming Lei <ming.lei@redhat.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v6 8/8] null_blk: Support configuring the maximum segment size
Date: Tue, 13 Jun 2023 08:52:52 +0200 [thread overview]
Message-ID: <20230613065252.GA15939@lst.de> (raw)
In-Reply-To: <2ec5270c-a913-44cf-3a45-0713e6c58224@acm.org>
On Mon, Jun 12, 2023 at 05:44:51PM -0700, Bart Van Assche wrote:
>
> Hi Damien,
>
> bio_split() enforces the max_sectors limit but not the max_segment_size
> limit.
bio_split() doesn't enforce any limit, but it's also not used by
null_blk or blk-mq.
bio_split_to_limits enforces max_segment_size in bvec_split_segs.
next prev parent reply other threads:[~2023-06-13 6:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 20:33 [PATCH v6 0/8] Support limits below the page size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 1/8] block: Use pr_info() instead of printk(KERN_INFO ...) Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 2/8] block: Prepare for supporting sub-page limits Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 3/8] block: Support configuring limits below the page size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 4/8] block: Make sub_page_limit_queues available in debugfs Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 5/8] block: Support submitting passthrough requests with small segments Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 6/8] block: Add support for filesystem requests and " Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 7/8] scsi_debug: Support configuring the maximum segment size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 8/8] null_blk: " Bart Van Assche
2023-06-12 22:17 ` Damien Le Moal
2023-06-13 0:44 ` Bart Van Assche
2023-06-13 6:47 ` Damien Le Moal
2023-06-13 6:52 ` Christoph Hellwig [this message]
2023-06-15 2:01 ` [PATCH v6 0/8] Support limits below the page size Bart Van Assche
2023-06-15 2:22 ` Jens Axboe
2023-06-15 4:15 ` Christoph Hellwig
2023-06-15 13:55 ` Bart Van Assche
2023-06-16 7:02 ` Christoph Hellwig
2023-06-16 20:26 ` Bart Van Assche
2023-06-16 21:48 ` Jens Axboe
2023-06-16 22:28 ` Bart Van Assche
2023-08-04 23:11 ` Juan Yescas
2023-06-15 14:16 ` Jens Axboe
2023-06-15 14:16 ` 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=20230613065252.GA15939@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dhavale@google.com \
--cc=dlemoal@kernel.org \
--cc=jyescas@google.com \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.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.