Hi, We implemented new two ioctls to allocate preferred blocks using inode PA. The old implementation idea is the following (b). http://marc.info/?l=linux-ext4&m=124962738211206&w=4 One is EXT4_IOC_CONTROL_PA that is to create or discard inode PA, and the other is EXT4_IOC_GET_PA that is to get inode PA information. 1. EXT4_IOC_CONTROL_PA EXT4_IOC_CONTROL_PA is used to create new inode PA, or to discard all inode PAs in the target inode. This means that we will be able to allocate the blocks we want. We have a plan to add a new feature to e4defrag with these ioctls. This feature improves read throughput when we read the files in the same directory by reallocating target files near their parent directory. 2. EXT4_IOC_GET_PA EXT4_IOC_GET_PA is used to get inode PA information. Moreover, when we create an inode PA, ext4_mb_new_inode_pa() merges contiguous inode PA if possible. This patch set consists of the following three patches. They can be applied to the ext4 patch queue: commit: 1dea5b6f540ad056d51d11cda71fa757cb44cbc4 [RFC][PATCH 0/3] ext4: inode preferred block allocation [RFC][PATCH 1/3] ext4: add EXT4_IOC_CONTROL_PA to create/discard inode PA [RFC][PATCH 2/3] ext4: sort and merge inode PA [RFC][PATCH 3/3] ext4: add EXT4_IOC_GET_PA to get inode PA information Any comments are very welcome. Best regards, Kazuya Mio -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
