From: Ming Lin <mlin@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
Kent Overstreet <kent.overstreet@gmail.com>,
Jens Axboe <axboe@kernel.dk>,
Dongsu Park <dongsu.park@profitbricks.com>
Subject: [PATCH v3 0/4] preparation for block layer simplification
Date: Thu, 23 Apr 2015 16:04:31 -0700 [thread overview]
Message-ID: <1429830275-6792-1-git-send-email-mlin@kernel.org> (raw)
I'd like to continue on Dongsu's effort to push Kent's block-stuff upstream.
This is a preparation series for simplifying block layer based on immutable
biovecs, a spin off of the v2 of simplifying patchset. [1] The original
goal of simplifying block layer was actually making generic_make_request()
accept arbitrarily sized bios, and pushing the splitting down to the
underlying drivers.
This patchset aims at cleaning up several parts that are independent of
core changes in the block layer. Doing that, it could be possible to
change block layer relatively easily without keeping up with many patches.
This patchset should be first applied prior to upcoming patchsets such as
"simplify block layer based on immutable biovecs." This patchset itself
should not bring any regression to end-users.
Changes in v3:
- rebase on top of Jen's bio-cnt branch
- drop patches 1 and 2 that were already upstream
- lib/iovec.c was gone, so move iov_count_pages to block/bio.c
Changes in v2:
- split up preparation patches from v1 into this separate series.
- In the patch 02, pass iov_iter by value to __bio_copy_iov(), and split
into read/write variants, as suggested by Christoph Hellwig.
- minor changes like writing more commit messages etc.
[1] https://lkml.org/lkml/2014/12/22/128
Kent Overstreet (4):
block: refactor iov_count_pages() from bio_{copy,map}_user_iov()
md/raid10: make sync_request_write() call bio_copy_data()
fs: make _submit_bh consistent with generic bio chaining
PM: submit bio in a sane way in cases without bio_chain
block/bio.c | 70 +++++++++++++++++++++++++++++++++-------------------------------------
drivers/md/raid10.c | 20 +++++---------------
fs/buffer.c | 4 ++--
kernel/power/block_io.c | 23 ++++++++++++++++++-----
4 files changed, 58 insertions(+), 59 deletions(-)
next reply other threads:[~2015-04-23 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 23:04 Ming Lin [this message]
2015-04-23 23:04 ` [PATCH v3 1/4] block: refactor iov_count_pages() from bio_{copy,map}_user_iov() Ming Lin
2015-04-24 7:06 ` Christoph Hellwig
2015-04-23 23:04 ` [PATCH v3 2/4] md/raid10: make sync_request_write() call bio_copy_data() Ming Lin
2015-04-24 7:08 ` Christoph Hellwig
2015-04-23 23:04 ` [PATCH v3 3/4] fs: make _submit_bh consistent with generic bio chaining Ming Lin
2015-04-24 7:25 ` Christoph Hellwig
2015-04-23 23:04 ` [PATCH v3 4/4] PM: submit bio in a sane way in cases without bio_chain Ming Lin
2015-04-24 16:17 ` Christoph Hellwig
2015-04-25 6:23 ` Ming Lin
2015-04-30 17:34 ` Pavel Machek
2015-05-01 17:21 ` Christoph Hellwig
2015-05-04 14:14 ` Rafael J. Wysocki
[not found] ` <20150430164717.GA21211@amd>
2015-05-05 9:23 ` Pavel Machek
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=1429830275-6792-1-git-send-email-mlin@kernel.org \
--to=mlin@kernel.org \
--cc=axboe@kernel.dk \
--cc=dongsu.park@profitbricks.com \
--cc=hch@infradead.org \
--cc=kent.overstreet@gmail.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