[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170421112458.GB12523@infradead.org>
Date: Fri, 21 Apr 2017 04:24:58 -0700
From: Christoph Hellwig <hch@...radead.org>
To: NeilBrown <neilb@...e.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 02/11] blk: make the bioset rescue_workqueue optional.
On Thu, Apr 20, 2017 at 03:38:48PM +1000, NeilBrown wrote:
> This patch converts bioset_create() and
> bioset_create_nobvec() to not create a workqueue so
> alloctions will never trigger punt_bios_to_rescuer(). It
> also introduces bioset_create_rescued() and
> bioset_create_nobvec_rescued() which preserve the old
> behaviour.
Why these super-early line breaks in the committ message? They make
the text much more awkware compared to say:
This patch converts bioset_create() and bioset_create_nobvec() to not
create a workqueue so alloctions will never trigger
punt_bios_to_rescuer(). It also introduces bioset_create_rescued() and
bioset_create_nobvec_rescued() which preserve the old behaviour.
> static struct bio_set *__bioset_create(unsigned int pool_size,
> unsigned int front_pad,
> - bool create_bvec_pool)
> + bool create_bvec_pool,
> + bool create_rescue_workqueue)
I'd much prefer a single new bioset_create with a bunch of flags
arguments over the number of new functions and these bool arguments.
Powered by blists - more mailing lists