On Wed, Jun 6, 2012 at 5:48 AM, Marcus Sorensen <shadowsor@xxxxxxxxx> wrote: > That's my thought. The checksumming speed doesn't remain static > regardless of what's being checksummed. If I want to calculate double > parity on a stripe that spans 30 disks I'd expect that to be more CPU > intensive than calculating double parity on a 3 disk stripe. If the checksumming speed differs wildly, then it seems odd that the kernel chooses the best checksumming algorithm before it knows what it is going to checksum. Would it not make more sense to defer deciding the algorithm till you know the actual task? /Ole -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
