linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Dmitry Monakhov <dmonakhov@openvz.org>,
	jaxboe@fusionio.com
Subject: Re: [PATCH 1/2] blkdev: Submit discard bio in batches in blkdev_issue_discard()
Date: Thu, 28 Apr 2011 09:29:29 -0400	[thread overview]
Message-ID: <x49sjt2ld1i.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104281007530.31735@dhcp-27-109.brq.redhat.com> (Lukas Czerner's message of "Thu, 28 Apr 2011 10:09:18 +0200 (CEST)")

Lukas Czerner <lczerner@redhat.com> writes:

> On Thu, 28 Apr 2011, Lukas Czerner wrote:
>
>> On Wed, 27 Apr 2011, Jeff Moyer wrote:
>> 
>> > Lukas Czerner <lczerner@redhat.com> writes:
>> > 
>> > > Currently we are waiting for every submitted REQ_DISCARD bio separately,
>> > > but it can have unwanted consequences of repeatedly flushing the queue,
>> > > so we rather submit bios in batches and wait for the entire batch, hence
>> > > narrowing the window of other ios going in.
>> > >
>> > > Use bio_batch_end_io() and struct bio_batch for that purpose, the same
>> > > is used by blkdev_issue_zeroout(). Also change bio_batch_end_io() so we
>> > > always set !BIO_UPTODATE in the case of error and remove the check for
>> > > bb, since we are the only user of this function and we always set this.
>> > >
>> > > Remove bio_get()/bio_put() from the blkdev_issue_discard() since
>> > > bio_alloc() and bio_batch_end_io() is doing the same thing, hence it is
>> > > not needed anymore.
>> > >
>> > > I have done simple dd testing with surprising results. The script I have
>> > > used is:
>> > >
>> > > for i in $(seq 10); do
>> > >         echo $i
>> > >         dd if=/dev/sdb1 of=/dev/sdc1 bs=4k &
>> > >         sleep 5
>> > > done
>> > > /usr/bin/time -f %e ./blkdiscard /dev/sdc1
>> > >
>> > > Running time of BLKDISCARD on the whole device:
>> > > with patch              without patch
>> > > 0.95                    15.58
>> > >
>> > > So we can see that in this artificial test the kernel with the patch
>> > > applied is approx 16x faster in discarding the device.
>> > 
>> > I don't see any major problems here.  I would like you to test
>> > explicitly for queue_flag_discard before submitting any bios, though.
>
> Btw, this is already in there:
>
> 	if (!blk_queue_discard(q))
> 		return -EOPNOTSUPP;
>
> at the top of the function.

Boy, how did I miss that?  ;-)

Cheers,
Jeff

      reply	other threads:[~2011-04-28 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 12:39 [PATCH 1/2] blkdev: Submit discard bio in batches in blkdev_issue_discard() Lukas Czerner
2011-04-20 12:39 ` [PATCH 2/2] blkdev: Simple cleanup in blkdev_issue_zeroout() Lukas Czerner
2011-04-27 14:05   ` Jeff Moyer
2011-04-27 13:57 ` [PATCH 1/2] blkdev: Submit discard bio in batches in blkdev_issue_discard() Jeff Moyer
2011-04-28  7:57   ` Lukas Czerner
2011-04-28  8:09     ` Lukas Czerner
2011-04-28 13:29       ` Jeff Moyer [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=x49sjt2ld1i.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=dmonakhov@openvz.org \
    --cc=jaxboe@fusionio.com \
    --cc=lczerner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).