| 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: <1179943732.4179.56.camel@coly-t43.site> Date: Thu, 24 May 2007 02:08:52 +0800 From: coly <colyli@...il.com> To: linux-ext4 <linux-ext4@...r.kernel.org> Cc: linux-kernel <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org> Subject: [RFC 5/5] inode reservation v0.1 (next step working) >>From the benchmark and the experimental inores patch on ext4, it can be found that inode reservation on ext4 is a good idea to be tried. One of the original idea of inode reservation is NOT modifying on-disk format. Current magic inode can make it, but use a magic inodes list to link each reserved inode block together is not a good idea. Indeed, this is a performance killer. 1, Therefor, group descriptor has to be modified to add a new member --- this new member records the lastest reserved inode in inode table of each block group. 2, Use rest room in magic inode (sizeof(ext4_inode) - sizeof(ext4_magic_inode)) to record other reserved inode blocks. This method can reduce number of magic inodes, which can minimize I/O for magic inodes. 3, Use magic inode cache. Most of the magic inode accessings are reading (not writing), therefore, caching can help to reduce most of the read I/O for magic inode. 4, Modify mke2fs to support new on-disk layout for inode reservation. Coly - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists