From: Jens Axboe <axboe@kernel.dk>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Shaohua Li <shli@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch]block: add plug for blkdev_issue_discard
Date: Mon, 08 Oct 2012 19:59:55 -0600 [thread overview]
Message-ID: <5073851B.6080002@kernel.dk> (raw)
In-Reply-To: <CAMM=eLcw8-r7iYSYG4uhJd_Q1rRYifye8T-Wv4PR9hQjF8j9gQ@mail.gmail.com>
On 2012-10-08 19:56, Mike Snitzer wrote:
> On Mon, Oct 8, 2012 at 9:11 PM, Shaohua Li <shli@kernel.org> wrote:
>> Now discard merge works, add plug for blkdev_issue_discard. This will help
>> discard request merge especially for raid0 case. In raid0, a big discard
>> request is split to small requests, and if correct plug is added, such small
>> requests can be merged in low layer.
>>
>> Signed-off-by: Shaohua Li <shli@fusionio.com>
>> ---
>> block/blk-lib.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> Index: linux/block/blk-lib.c
>> ===================================================================
>> --- linux.orig/block/blk-lib.c 2012-09-28 15:09:38.655327319 +0800
>> +++ linux/block/blk-lib.c 2012-10-09 08:45:04.358598888 +0800
>> @@ -48,6 +48,7 @@ int blkdev_issue_discard(struct block_de
>> struct bio_batch bb;
>> struct bio *bio;
>> int ret = 0;
>> + struct blk_plug plug;
>>
>> if (!q)
>> return -ENXIO;
>> @@ -81,6 +82,7 @@ int blkdev_issue_discard(struct block_de
>> bb.flags = 1 << BIO_UPTODATE;
>> bb.wait = &wait;
>>
>> + blk_start_plug(&plug);
>> while (nr_sects) {
>> unsigned int req_sects;
>> sector_t end_sect;
>> @@ -117,6 +119,7 @@ int blkdev_issue_discard(struct block_de
>> atomic_inc(&bb.done);
>> submit_bio(type, bio);
>> }
>> + blk_finish_plug(&plug);
>>
>> /* Wait for bios in-flight */
>> if (!atomic_dec_and_test(&bb.done))
>
> That plug looks rather coarse-grained. Any adverse affects when mkfs
> discards an entire (large) raid0 device? (I suspect not but figured
> I'd ask)
Block core auto-unplugs after a certain depth is reached. So it's better
to make it coarse than try to second guess when to unplug.
--
Jens Axboe
prev parent reply other threads:[~2012-10-09 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 1:11 [patch]block: add plug for blkdev_issue_discard Shaohua Li
2012-10-09 1:56 ` Mike Snitzer
2012-10-09 1:59 ` Jens Axboe [this message]
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=5073851B.6080002@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.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