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: <20120702030310.GA2406@gmail.com> Date: Mon, 2 Jul 2012 11:03:11 +0800 From: Zheng Liu <gnehzuil.liu@...il.com> To: Andreas Dilger <adilger@...ger.ca> Cc: Ric Wheeler <rwheeler@...hat.com>, Eric Sandeen <sandeen@...hat.com>, Theodore Ts'o <tytso@....edu>, Fredrick <fjohnber@...o.com>, linux-ext4@...r.kernel.org, wenqing.lz@...bao.com Subject: Re: ext4_fallocate On Fri, Jun 29, 2012 at 01:02:35PM -0600, Andreas Dilger wrote: > There is already code for this in the ext4 uninit extent handling. > Currently the limit is 15(?) blocks, to inflate the write size up > to zero-fill a 64kB chunk on 4kB blocksize filesystems. I wouldn't > object to increasing this to zero out a full 1MB (aligned) chunk > under random IO cases. I agree with you that we can increase it to 1MB chunk, and I will run some tests to see the result. In addition, I am thinking whether we can provide a parameter in sysfs or some other places to adjust this value dynamically. Regards, Zheng -- 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