From: NeilBrown <neilb@suse.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-block <linux-block@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Shaohua Li <shli@kernel.org>
Subject: Re: [GIT PULL] Block changes for 4.18-rc
Date: Tue, 05 Jun 2018 08:52:32 +1000 [thread overview]
Message-ID: <8736y2p3kf.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180604212100.GB30325@kmo-pixel>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
On Mon, Jun 04 2018, Kent Overstreet wrote:
> On Tue, Jun 05, 2018 at 07:16:51AM +1000, NeilBrown wrote:
>> I really should get back to BIOSET_NEED_RESCUER and see if I can discard
>> it completely.
>> Kent - the only remaining user is bcache, and the main reason I haven't
>> removed it is that I cannot follow the code (or at least, I couldn't
>> last time I tried). Are you able to see if it is still needed?
>
> Oh man, rescueurs make my head hurt. I remember you changed something so that
> they weren't needed most of the time, but I can't remember what you did - can
> you remind me what that was and whatever else you can remember offhand?
(and closures make my head hurt :-)
There were two closely related changes.
One is make sure that generic_make_request processed bios strictly
in a depth-first order. The other is to ensure that all (stacking)
block device drivers never block in their make_request_fn waiting
for something that have themselves submitted.
Together these mean that a thread in generic_make_request will never
block waiting for a bio that might be queued in current->bio_list.
The bio chosen by generic_make_request will be a leaf and won't depend
on anything else in the list, and the handler for that request won't
block after submitting a lower-level request.
The second property is the important one for drivers and the one we
need to ensure that bcache follows.
A common bad pattern is something like:
while (too_big(bio)) {
split = bio_spilt(bio,...))
process(split)
}
process(bio)
That needs to be more like
if (too_big(bio)) {
split = bio_split(bio,...);
generic_make_request(bio);
bio = split;
}
process(bio)
so that generic_make_request() gets to do that while-loop
and can control the order in which bios are handled.
I cannot convince myself that bcache doesn't have something similar to
that while loop (structured with closures).
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-04 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 0:42 [GIT PULL] Block changes for 4.18-rc Jens Axboe
2018-06-04 15:51 ` Linus Torvalds
2018-06-04 15:54 ` Jens Axboe
2018-06-04 16:24 ` Linus Torvalds
2018-06-04 18:20 ` Tejun Heo
2018-06-04 18:22 ` Linus Torvalds
2018-06-04 18:25 ` Jens Axboe
2018-06-04 19:04 ` Kent Overstreet
2018-06-05 0:42 ` Linus Torvalds
2018-06-05 0:44 ` Linus Torvalds
2018-06-05 0:56 ` Kent Overstreet
2018-06-05 1:00 ` Linus Torvalds
2018-06-07 1:45 ` Jens Axboe
2018-06-04 21:16 ` NeilBrown
2018-06-04 21:21 ` Kent Overstreet
2018-06-04 22:52 ` NeilBrown [this message]
2018-06-05 0:34 ` Kent Overstreet
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=8736y2p3kf.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=shli@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