From: Theodore Ts'o <tytso@mit.edu>
To: Andrey Sidorov <qrxd43@motorola.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH V3] ext4: speed-up releasing blocks on commit
Date: Tue, 9 Apr 2013 12:36:48 -0400 [thread overview]
Message-ID: <20130409163648.GA5980@thunk.org> (raw)
In-Reply-To: <1364498818-17909-1-git-send-email-qrxd43@motorola.com>
On Thu, Mar 28, 2013 at 11:26:58PM +0400, Andrey Sidorov wrote:
> Improve mb_free_blocks speed by clearing entire range at once instead of
> iterating over each bit. Freeing block-by-block also makes buddy bitmap
> subtree flip twice making most of the work a no-op. Very few bits in buddy
> bitmap require change, e.g. freeing entire group is a 1 bit flip only.
> As a result, releasing blocks of 60G file now takes 5ms instead of 2.7s.
> This is especially good for non-preemptive kernels as there is no
> rescheduling during release.
>
> Signed-off-by: Andrey Sidorov <qrxd43@motorola.com>
Thanks, added to the dev branch for testing.
- Ted
prev parent reply other threads:[~2013-04-09 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 19:26 [PATCH V3] ext4: speed-up releasing blocks on commit Andrey Sidorov
2013-04-09 16:36 ` Theodore Ts'o [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=20130409163648.GA5980@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 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).