linux-ext4 - [RFC] enable ext4 allocate blocks across group boundary

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGBYx2aETBVb2hMyEBC91meRwr_Z+cnMNwF+ZBU4nk1PdedygA@mail.gmail.com>
Date:	Thu, 15 Mar 2012 08:52:35 +0800
From:	Yongqiang Yang <xiaoqiangnk@...il.com>
To:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: [RFC] enable ext4 allocate blocks across group boundary

Hello List,

Here is a proposal to enable ext4 allocate blocks across group boundary.

Now ext4 allocates blocks within a single block group by locking a
group.   Flex_bg puts metadata blocks together, as a result,it
enlarges contiguous blocks.  So we can enable ext4 allocate blocks
within a flex block group. Inode allocation takes group lock as block
allocation,  I am not sure if we should allocate inode within single
group as before.

If we do this, then the new group boundary will be flex block group
boundary.  I am not sure if it is worth doing.

Any ideas?

-- 
Best Wishes
Yongqiang Yang
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html