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
| ||
|
Message-ID: <op.xao2fube0ncgu9@vitalif.vhome> Date: Mon, 03 Feb 2014 11:15:20 +0400 From: "Vitaliy Filippov" <vitalif@...rcmc.ru> To: "Andreas Dilger" <adilger@...ger.ca> Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "Bastien Traverse" <bastien.traverse@...il.com> Subject: Re: mke2fs options for large media archive filesystem > I would say that bigalloc is probably not what you want for an archival > system. It is relatively new and the space savings is minimal. It is > mostly for filesystems that need to allocate and free large files > rapidly. And does it introduce any memory usage benefit? Maybe not on a 1TB, but on a 32TB partition? :) I.e. does the kernel keep full block bitmap (or maybe a tree of blocks?) in memory, or does it read parts of it when they're needed? -- With best regards, Vitaliy Filippov -- 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
Powered by blists - more mailing lists