From: Jens Axboe <axboe@kernel.dk>
To: NeilBrown <neilb@suse.com>, Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/11] blk: make the bioset rescue_workqueue optional.
Date: Mon, 1 May 2017 08:02:13 -0600 [thread overview]
Message-ID: <583a23d7-3d5f-e280-6ef4-a7fec84359e2@kernel.dk> (raw)
In-Reply-To: <87tw55qigs.fsf@notabene.neil.brown.name>
On 04/30/2017 11:00 PM, NeilBrown wrote:
> On Mon, Apr 24 2017, Christoph Hellwig wrote:
>
>> On Mon, Apr 24, 2017 at 11:51:01AM +1000, NeilBrown wrote:
>>>
>>> I was following the existing practice exemplified by
>>> bioset_create_nobvec().
>>
>> Which is pretty ugly to start with..
>
> That is a matter of personal taste.
> As such, it is up to the maintainer to change it if they want it
> changed.
>
>>
>>> By not changing the signature of the function, I can avoid touching
>>> quite a few places where it is called.
>>
>> There are 13 callers of bioset_create and one caller of
>> bioset_create_nobvec, and your series touches many of those.
>>
>> So just adding a flags argument to bioset_create and passing
>> BIOSET_NEED_BVECS and BIOSET_NEED_RESUER flags to it doesn't seem
>> to much of an effort, and it's going to create a much nicer and easier
>> to extend interface.
>
> If someone else submitted a patch to discard bioset_create_nobvec in
> favour of BIOSET_NEED_BVECS and got it accepted, then I would rebase my
> series on that. As it is, I'm basing my patches on the style currently
> present in the tree.
>
> Of course, if Jens says he'll only take my patches if I change to style
> to match your preference, I'll do that.
I generally tend to prefer tree wide cleanups to improve our APIs, even
if it does cause an extra bit of pain. Would you mind doing that as a
prep patch?
--
Jens Axboe
next prev parent reply other threads:[~2017-05-01 14:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 5:38 [PATCH 00/11] block: assorted cleanup for bio splitting and cloning NeilBrown
2017-04-20 5:38 ` [PATCH 01/11] blk: remove bio_set arg from blk_queue_split() NeilBrown
2017-04-21 11:21 ` Christoph Hellwig
2017-04-21 15:14 ` Ming Lei
2017-04-22 9:16 ` Javier González
2017-04-24 2:32 ` NeilBrown
2017-04-20 5:38 ` [PATCH 02/11] blk: make the bioset rescue_workqueue optional NeilBrown
2017-04-21 11:24 ` Christoph Hellwig
2017-04-24 1:51 ` NeilBrown
2017-04-24 15:10 ` Christoph Hellwig
2017-05-01 5:00 ` NeilBrown
2017-05-01 14:02 ` Jens Axboe [this message]
2017-05-02 3:33 ` NeilBrown
2017-04-20 5:38 ` [PATCH 07/11] pktcdvd: use bio_clone_fast() instead of bio_clone() NeilBrown
2017-04-21 11:29 ` Christoph Hellwig
2017-04-20 5:38 ` [PATCH 05/11] rbd: " NeilBrown
2017-04-21 11:31 ` Christoph Hellwig
2017-04-20 5:38 ` [PATCH 03/11] blk: use non-rescuing bioset for q->bio_split NeilBrown
2017-04-21 11:25 ` Christoph Hellwig
2017-04-20 5:38 ` [PATCH 04/11] block: Improvements to bounce-buffer handling NeilBrown
2017-04-21 11:28 ` Christoph Hellwig
2017-04-21 15:39 ` Ming Lei
2017-04-20 5:38 ` [PATCH 06/11] drbd: use bio_clone_fast() instead of bio_clone() NeilBrown
2017-04-21 11:30 ` Christoph Hellwig
2017-04-20 5:38 ` [PATCH 09/11] bcache: use kmalloc to allocate bio in bch_data_verify() NeilBrown
2017-04-21 11:31 ` Christoph Hellwig
2017-04-21 11:32 ` Kent Overstreet
2017-04-21 15:41 ` Ming Lei
2017-04-20 5:38 ` [PATCH 08/11] xen-blkfront: remove bio splitting NeilBrown
2017-04-20 10:00 ` Roger Pau Monné
2017-04-21 11:36 ` Christoph Hellwig
2017-04-21 11:46 ` Roger Pau Monne
2017-04-20 5:38 ` [PATCH 11/11] block: don't check for BIO_MAX_PAGES in blk_bio_segment_split() NeilBrown
2017-04-21 11:34 ` Christoph Hellwig
2017-04-21 15:48 ` Ming Lei
2017-04-24 3:16 ` NeilBrown
2017-04-24 3:14 ` NeilBrown
2017-04-20 5:38 ` [PATCH 10/11] block: remove bio_clone() and all references NeilBrown
2017-04-21 11:32 ` Christoph Hellwig
2017-04-21 15:43 ` 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=583a23d7-3d5f-e280-6ef4-a7fec84359e2@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.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).