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: <7A86A0B9-5C08-42C9-A136-010CAAE384A1@dilger.ca>
Date: Mon, 3 Feb 2014 14:09:13 -0700
From: Andreas Dilger <adilger@...ger.ca>
To: Vitaliy Filippov <vitalif@...rcmc.ru>
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
On Feb 3, 2014, at 12:15 AM, Vitaliy Filippov <vitalif@...rcmc.ru> wrote:
>> 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?
The kernel dynamically loads bitmaps when needed.
Cheers, Andreas
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists