From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH v2 2/3] block: Split and submit bios in LBA order
Date: Tue, 21 Mar 2023 07:05:30 +0100 [thread overview]
Message-ID: <20230321060530.GC18078@lst.de> (raw)
In-Reply-To: <20230321060307.GB18078@lst.de>
On Tue, Mar 21, 2023 at 07:03:07AM +0100, Christoph Hellwig wrote:
> > + if (current->bio_list) {
> > + /*
> > + * The caller will submit the first half ('split')
> > + * before the second half ('bio').
> > + */
> > + bio_chain(split, bio);
> > + submit_bio_noacct(bio);
> > + return split;
> > + }
> > + /*
> > + * Submit the first half ('split') let the caller submit the
> > + * second half ('bio').
> > + */
> > + *nr_segs = bio_chain_nr_segments(bio, lim);
> > + bio_chain(split, bio);
> > + submit_bio_noacct(split);
>
> I'm really confused on why you want to change the behavior here
> for the case where run in a stacking context vs not, and neither
> the comments nor the commit log help me trying to figure out why.
In fact I wonder how you managed to get into __bio_split_to_limits
wtih a NULL current->bio_list at all.
next prev parent reply other threads:[~2023-03-21 6:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 23:49 [PATCH v2 0/3] Submit zoned requests in LBA order per zone Bart Van Assche
2023-03-20 23:49 ` [PATCH v2 1/3] block: Split blk_recalc_rq_segments() Bart Van Assche
2023-03-20 23:49 ` [PATCH v2 2/3] block: Split and submit bios in LBA order Bart Van Assche
2023-03-21 6:03 ` Christoph Hellwig
2023-03-21 6:05 ` Christoph Hellwig [this message]
2023-03-21 18:44 ` Bart Van Assche
2023-03-23 8:22 ` Christoph Hellwig
2023-03-20 23:49 ` [PATCH v2 3/3] block: Preserve LBA order when requeuing Bart Van Assche
2023-03-21 5:58 ` Christoph Hellwig
2023-03-21 14:46 ` Bart Van Assche
2023-03-23 8:19 ` Christoph Hellwig
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=20230321060530.GC18078@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jaegeuk@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.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.