From: Mason <mpeg.blue@free.fr>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
"Theodore Ts'o" <tytso@mit.edu>,
"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: Tue, 05 Aug 2014 14:06:03 +0200 [thread overview]
Message-ID: <53E0C8AB.7090405@free.fr> (raw)
In-Reply-To: <6910CF48-15F8-4218-8881-06899D7C56A5@dilger.ca>
On 05/08/2014 00:55, 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 of bits.
>
> 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 ancient times when the buddy bitmaps were
> stored on disk instead of being regenerated only at mount time.
Are there any other tests you'd like me to run?
(I will be permanently losing access to this platform in a few days.)
--
Regards.
prev parent reply other threads:[~2014-08-05 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 14:09 After unlinking a large file on ext4, the process stalls for a long time Mason
2014-07-16 15:16 ` John Stoffel
2014-07-16 17:16 ` Mason
2014-07-16 20:18 ` John Stoffel
2014-07-16 21:46 ` Mason
2014-07-17 3:37 ` 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
2014-08-05 21:54 ` Andreas Dilger
2014-08-05 12:06 ` Mason [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=53E0C8AB.7090405@free.fr \
--to=mpeg.blue@free.fr \
--cc=adilger@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.