search for: taoma

I've read fs/ocfs2/dlm/dlmcommon.h to study the structure of dlm_migratable_lockres. However, I may find a typo for the DLM_MIG_LOCKRES_MAX_LEN, the NET_MAX_PAYLOAD_BYTES should be O2NET_MAX_PAYLOAD_BYTES, I think. In comments, the sizeof(net_msg) should be sizeof(o2net_msg) by referring to fs/ocfs2/cluster/tcp.h. Signed-off-by: Jeff Liu <jeff.liu at oracle.com> ---

...umn is the result without inode allocation patches, and the second one with inode allocation patched enabled. You see we have great improvement with the second "ls -lR". echo 'y'|mkfs.ocfs2 -b 4K -C 4K -M local /dev/sda11 mount -t ocfs2 /dev/sda11 /mnt/ocfs2/ time tar jxvf /home/taoma/linux-2.6.28.tar.bz2 -C /mnt/ocfs2/ 1>/dev/null real 0m20.548s 0m20.106s umount /mnt/ocfs2/ echo 2 > /proc/sys/vm/drop_caches mount -t ocfs2 /dev/sda11 /mnt/ocfs2/ time ls -lR /mnt/ocfs2/ 1>/dev/null real 0m13.965s 0m13.766s umount /mnt/ocfs2/ echo 2 > /proc/sys/vm/drop_caches mount...

In ocfs2, the inode block search looks for the "emptiest" inode group to allocate from. So if an inode alloc file has many equally (or almost equally) empty groups, new inodes will tend to get spread out amongst them, which in turn can put them all over the disk. This is undesirable because directory operations on conceptually "nearby" inodes force a large number of seeks. So