mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@canonical.com>
To: Jens Axboe <axboe@fb.com>, linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Anton Altaparmakov <anton@tuxera.com>,
	xfs@oss.sgi.com, Dave Chinner <david@fromorbit.com>,
	drbd-dev@lists.linbit.com,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	Boaz Harrosh <boaz@plexistor.com>
Subject: [PATCH v1 0/8] block: prepare for multipage bvecs
Date: Thu, 31 Mar 2016 00:17:09 +0800	[thread overview]
Message-ID: <1459354637-17415-1-git-send-email-ming.lei@canonical.com> (raw)

Hi,

Interests[1] have been shown in multipage bvecs, so this patchset
try to prepare for the support and do two things:

1) the 1st 4 patches use bvec iterator to implement iterate_bvec(),
then we can drop the non-standard way for iterating bvec, which
can be thought as a good cleanup for lib/iov_iter.c

2) remove BIO_MAX_SECTORS & BIO_MAX_SIZE, and now there is only
one user for each. Once multipage bvecs is introduced, one bio
may hold lots of sectors, and we should always use sort of BIO_MAX_VECS
which should be introduced in future and is similiar with current
BIO_MAX_PAGES.

xfstests(-a auto) have been run and no regression found by this
patchset against linus v4.6-rc1-next-20160329.

V1:
	- don't move BIO_MAX_* to bvec_iter.h as pointed out by Christoph
	- run xfstests against v4.6-rc1-next-20160329
	- add Reviewed-by
	- for 1,4 and 5, Reviewd-by not added, Christoph still expressed
	'this looks fine to me.'

 drivers/block/drbd/drbd_int.h |  4 ++--
 fs/xfs/xfs_buf.c              |  4 +---
 include/linux/bio.h           | 53 +----------------------------------------
 include/linux/blk_types.h     |  4 ++--
 include/linux/bvec_iter.h     | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 lib/iov_iter.c                | 31 +++++++++---------------
 6 files changed, 92 insertions(+), 79 deletions(-)

Thanks,
Ming

             reply	other threads:[~2016-03-30 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 16:17 Ming Lei [this message]
2016-03-30 16:17 ` [PATCH v1 1/8] block: move bvec iterator into include/linux/bvec_iter.h Ming Lei
2016-03-30 16:17 ` [PATCH v1 2/8] block: make 'struct bvec_iter' not depend on CONFIG_BLOCK Ming Lei
2016-03-30 17:19   ` Christoph Hellwig
2016-03-31  1:02     ` Ming Lei
2016-03-31  7:52       ` Christoph Hellwig
2016-04-01  0:31         ` Ming Lei
2016-03-30 16:17 ` [PATCH v1 3/8] block: mark 1st parameter of bvec_iter_advance as const Ming Lei
2016-03-30 16:17 ` [PATCH v1 4/8] iov_iter: use bvec iterator to implement iterate_bvec() Ming Lei
2016-03-30 16:17 ` [PATCH v1 5/8] fs: xfs: replace BIO_MAX_SECTORS with BIO_MAX_PAGES Ming Lei
2016-03-30 16:17 ` [PATCH v1 6/8] block: bio: remove BIO_MAX_SECTORS Ming Lei
2016-03-30 16:17 ` [PATCH v1 7/8] block: drbd: avoid to use BIO_MAX_SIZE Ming Lei
2016-03-30 16:17 ` [PATCH v1 8/8] block: bio: remove BIO_MAX_SIZE Ming Lei

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=1459354637-17415-1-git-send-email-ming.lei@canonical.com \
    --to=ming.lei@canonical.com \
    --cc=anton@tuxera.com \
    --cc=axboe@fb.com \
    --cc=boaz@plexistor.com \
    --cc=david@fromorbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=hch@infradead.org \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs@oss.sgi.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 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®