From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Anssi Hannula <anssi.hannula@iki.fi>
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH e2fsprogs] resize2fs: avoid constantly flushing while moving blocks
Date: Wed, 17 Apr 2024 00:33:40 -0400 [thread overview]
Message-ID: <171332777784.2749069.4830925403023907737.b4-ty@mit.edu> (raw)
In-Reply-To: <20231107094920.4056281-1-anssi.hannula@iki.fi>
On Tue, 07 Nov 2023 11:46:53 +0200, Anssi Hannula wrote:
> resize2fs block_mover() flushes data after each extent and, curiously,
> only if progress indicator is enabled, every inode_blocks_per_group
> blocks.
>
> This significantly affects performance, e.g. on a tested large
> filesystem on top of MD-RAID6+LVM+dm-crypt these flush calls reduce the
> operation rate from approx. 500MB/s to 5MB/s, causing extremely long
> shrinking times for large size deltas (70TB in my case).
>
> [...]
Applied, thanks!
[1/1] resize2fs: avoid constantly flushing while moving blocks
commit: e0e6b13d0ea7330234a6fe51ec3ba13ef884735e
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-04-17 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 9:46 [PATCH e2fsprogs] resize2fs: avoid constantly flushing while moving blocks Anssi Hannula
2024-04-17 4:33 ` 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=171332777784.2749069.4830925403023907737.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=anssi.hannula@iki.fi \
--cc=linux-ext4@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 read-only IMAP folder(s) and NNTP newsgroup(s).