On Tuesday November 12, jakob@unthought.net wrote: > > You might want to consider using huge chunk-sizes when reading, but > making sure that writes can be made on "sub-chunks" - so that one could > run a RAID-6 with a 128k chunk size, yet have writes performed on 4k > chunks. This is important for performance on both read and write, but > it is an optimization the current RAID-5 code lacks. Either I misunderstand your point, or you misunderstand the code. A 4k write request will cause a 4k write to a data block and a 4k write to a parity block, no matter what the chunk size is. (There may also be pre-reading, and possibly several 4k writes will share a parity block update). I see no lacking optimisation, but if you do, I would be keen to hear a more detailed explanation. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
