From: NeilBrown <neilb@suse.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 4] Change prototype for bi_end_io
Date: Thu, 27 Sep 2007 17:20:01 +1000 [thread overview]
Message-ID: <20070927171111.3251.patches@notabene> (raw)
Hi Jens,
here are a few more patches from my set that makes various changes to bio
submission and handling.
These change the ->bi_end_io prototype so that
1/ no 'size' is passed
2/ there is no return value.
The 'size' is not really of interest to any bi_end_io handler in existance.
It is really only an internal detail to the "request" handling in ll_rw_blk
and lower levels.
The return value is completely unused.
After these patches, ->bi_end_io is only ever called once per bio.
Note that the last patch makes lots and lots of simple changes. I
think I have found all the right places, but any recently added
device drivers might still be using the old bi_end_io prototype.
I'll grep again after these patches are in your tree.
That patches are against linux-block as of an hour ago.
Thanks,
NeilBrown
Net result of the 4 patches:
46 files changed, 166 insertions(+), 385 deletions(-)
[PATCH 001 of 4] Remove flush_dry_bio_endio
[PATCH 002 of 4] Only call bi_end_io once for any bio.
[PATCH 003 of 4] Don't decrement bi_size in bio_endio.
[PATCH 004 of 4] Drop 'size' argument from bio_endio and bi_end_io.
next reply other threads:[~2007-09-27 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 7:20 NeilBrown [this message]
2007-09-27 7:20 ` [PATCH 001 of 4] Remove flush_dry_bio_endio NeilBrown
2007-09-27 7:20 ` [PATCH 002 of 4] Only call bi_end_io once for any bio NeilBrown
2007-09-27 7:20 ` [PATCH 003 of 4] Don't decrement bi_size in bio_endio NeilBrown
2007-09-27 7:20 ` [PATCH 004 of 4] Drop 'size' argument from bio_endio and bi_end_io NeilBrown
2007-09-27 11:13 ` [PATCH 000 of 4] Change prototype for bi_end_io Jens Axboe
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=20070927171111.3251.patches@notabene \
--to=neilb@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®