From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Mason <mpeg.blue@free.fr>, "Lukáš Czerner" <lczerner@redhat.com>,
"Ext4 Developers List" <linux-ext4@vger.kernel.org>
Subject: Re: After unlinking a large file on ext4, the process stalls for a long time
Date: Mon, 4 Aug 2014 22:33:00 -0400 [thread overview]
Message-ID: <20140805023300.GE5263@thunk.org> (raw)
In-Reply-To: <6910CF48-15F8-4218-8881-06899D7C56A5@dilger.ca>
On Tue, Aug 05, 2014 at 12:55:14AM +0200, Andreas Dilger wrote:
> It would be possible to optimize mb_free_blocks() by having it
> clear a whole word at a time instead of a series if bits.
It looks like we're doing this already in mb_test_and_clear_bits(),
aren't we?
> I thought that was done already, but it doesn't appear to be the case.
> Also, it isn't clear that the bit "normalization" is needed anymore.
> This was done back in the aniceint times when the buddy bitmaps were stored on disk instead of being regenerated only at mount time.
I'm not sure what you mean by this; the only reference I can find
normalization is with normalizing requests?
- Ted
next prev parent reply other threads:[~2014-08-05 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53C687B1.30809@free.fr>
[not found] ` <21446.38705.190786.631403@quad.stoffel.home>
[not found] ` <53C6B38A.3000100@free.fr>
2014-07-17 3:37 ` After unlinking a large file on ext4, the process stalls for a long time Andreas Dilger
2014-07-17 10:30 ` Mason
2014-07-17 10:40 ` Lukáš Czerner
2014-07-17 11:17 ` Mason
2014-07-17 13:37 ` Theodore Ts'o
2014-07-17 16:07 ` Mason
2014-07-17 16:32 ` Mason
2014-07-18 9:29 ` Lukáš Czerner
[not found] ` <53DF9918.3010206@free.fr>
2014-08-04 22:55 ` Andreas Dilger
2014-08-05 2:33 ` Theodore Ts'o [this message]
2014-08-05 21:54 ` Andreas Dilger
2014-08-05 12:06 ` Mason
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=20140805023300.GE5263@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mpeg.blue@free.fr \
/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).