All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Andrey Sidorov <qrxd43@motorola.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] ext4: speed-up truncate/unlink
Date: Tue, 18 Sep 2012 00:10:06 -0400	[thread overview]
Message-ID: <20120918041006.GC32195@thunk.org> (raw)
In-Reply-To: <CAA0+VHzw55=4X43GK9RkRK_q4qmzR8KyqrrFidQMCPb6r4nPeA@mail.gmail.com>

On Tue, Sep 18, 2012 at 01:00:30AM +0400, Andrey Sidorov wrote:
> Do not iterate over data blocks scanning for bh's to forget as they're
> never exist. This improves time taken by unlink / truncate syscall.
> Tested by continuously truncating file that is being written by dd.
> Another test is rm -rf of linux tree while tar unpacks it. With
> ordered data mode condition unlikely(!tbh) was always met in
> ext4_free_blocks. With journal data mode tbh was found only few times,
> so optimisation is also possible.

Thanks for this patch.  It's good you did the testing, although from a
theoretical point of view I'm sure it's sound because the only case
where journal=data mode will there be data blocks in the buffer cache.
In the other cases, the data is cached in the page cache, so it's a
waste of time looking up the blocks so they can be bforgotten.

The one thing which is missing from your patch is a Signed-off-by:
footer.  This has a specific legal meaning.  See:

	http://elinux.org/Developer_Certificate_Of_Origin

You don't need to resend this patch, though; just reply with an
acknowledgement that you agree to add your DCO to the patch:

Signed-off-by: Andrey Sidorov <qrxd43@motorola.com>


Thanks for contributing to the ext4 file system!

						- Ted

  reply	other threads:[~2012-09-18  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 21:00 [PATCH RFC 1/2] ext4: speed-up truncate/unlink Andrey Sidorov
2012-09-18  4:10 ` Theodore Ts'o [this message]
2012-09-18 18:17   ` Andrey Sidorov
2012-09-19 18:16     ` Theodore Ts'o

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=20120918041006.GC32195@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=qrxd43@motorola.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.