linux-ext4 - Question about BIGALLOC

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: <CAFZ0FUUH85yWoVZ3XpMMYjhiaDrV9QQRSrLsAomXhH8uG_duBg@mail.gmail.com>
Date:	Fri, 5 Aug 2011 15:59:01 +0800
From:	Robin Dong <hao.bigrat@...il.com>
To:	"Ted Ts'o" <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Question about BIGALLOC

Hi, Ted

I am doing some test of BIGALLOC using "next" branch of e2fsprogs and
kernel (3.0) with 23 bigalloc-patches.

Everything seems to work, but I have a question:
the "ee_len" of "struct ext4_extent" is used to indicate block numbers
not cluster,
an ext4_extent in 4K-block-size filesystem can only hold 128MB space at most
even with BIGALLOC feature enabled, so we don't have any benefit from
this for a file with large number of blocks.

Is this the design behavior or you will change it in the next version?

-- 
--
Best Regard
Robin Dong
--
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