One very interesting optimization would be to profile the metadata workload where you got the slowdown and try to figure out which fields were most commonly updated. If it's some superblock fields or similar maybe those could get their separate crcs that could be separatedly computed at much lower cost. -Andi -- 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
