Received-SPF: pass (google.com: domain of linux-ext4+bounces-2123-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Li Dongyang <dongyangli@ddn.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, adilger@dilger.ca
Subject: Re: [PATCH] mke2fs: batch zeroing inode table
Date: Tue, 16 Apr 2024 22:03:33 -0400
Message-ID: <171328638215.2734906.8018789914145416497.b4-ty@mit.edu>
In-Reply-To: <20230904045806.827621-1-dongyangli@ddn.com>
References: <20230904045806.827621-1-dongyangli@ddn.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


On Mon, 04 Sep 2023 14:58:06 +1000, Li Dongyang wrote:
> For flex_bg enabled fs, we could merge the
> inode table blocks into a contiguous range,
> this improves mke2fs time on large devices
> when lazy_itable_init is disabled.
> 
> On a 977TB device, unpatched mke2fs was running
> for 449m10s before getting terminated manually.
> strace shows huge number of fallocate, given the
> offset from fallocate it has done 41% of the inode
> tables, the estimated time needed would be 1082m.
> 
> [...]

Applied, thanks!

[1/1] mke2fs: batch zeroing inode table
      commit: a192f4f344456c2390ce946b4a71db0b85ce5665

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>