From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Shaohua Li <shli@kernel.org>, Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>, NeilBrown <neilb@suse.com>
Subject: Re: [PATCH 2/4] md: introduce bio_clone_slow_mddev_partial()
Date: Mon, 6 Feb 2017 00:52:59 -0800 [thread overview]
Message-ID: <20170206085259.GA6411@infradead.org> (raw)
In-Reply-To: <1486275733-7268-3-git-send-email-tom.leiming@gmail.com>
> +struct bio *bio_clone_slow_mddev_partial(struct bio *bio, gfp_t gfp_mask,
> + struct mddev *mddev, int offset,
> + int size)
> +{
> + struct bio_set *bs;
> +
> + if (!mddev || !mddev->bio_set)
> + bs = fs_bio_set;
> + else
> + bs = mddev->bio_set;
> +
> + return bio_clone_bioset_partial(bio, gfp_mask, bs, offset << 9,
> + size << 9);
> +}
> +EXPORT_SYMBOL_GPL(bio_clone_slow_mddev_partial);
As far as I can tell the caller always has a mddev, and an active
mddev always has a bio_set. So let's just skip this wrapper.
next prev parent reply other threads:[~2017-02-06 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 6:22 [PATCH 0/4] md: use bio_clone_fast() Ming Lei
2017-02-05 6:22 ` [PATCH 1/4] block: introduce bio_clone_bioset_partial() Ming Lei
2017-02-05 6:22 ` [PATCH 2/4] md: introduce bio_clone_slow_mddev_partial() Ming Lei
2017-02-06 8:52 ` Christoph Hellwig [this message]
2017-02-05 6:22 ` [PATCH 3/4] md/raid1: use bio_clone_slow_mddev_partial in case of write behind Ming Lei
2017-02-05 6:22 ` [PATCH 4/4] md: fast clone bio in bio_clone_mddev() Ming Lei
2017-02-06 8:54 ` Christoph Hellwig
2017-02-06 10:43 ` Ming Lei
2017-02-06 14:24 ` 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=20170206085259.GA6411@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=shli@kernel.org \
--cc=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).