On Mon, Jun 29, 2015 at 12:30 PM, Daniel Swarbrick <daniel.swarbrick@xxxxxxxxxxxxxxxx> wrote: > On 29/06/15 12:51, Gregory Farnum wrote: >> >> Yes, we have our own CRC32 checksum because loooong ago (before I >> started!) Sage saw a lot of network corruption that wasn't being >> caught by the TCP checksums so he added some to the Ceph message >> stream. I can't tell you with any authority whatsoever how common that >> problem is, but I don't think we're turning them off by default in >> upstream. :) > > If the CRC32 implementation in Ceph is that dated (particularly the > software implementations that will be used on AMD hardware), would it be > worth checking out some of the updated implementations, such as the > slice-by-16 or chunked methods? Possibly? I really don't know anything about this. :) There have been several changes to add new implementations (aarch64 and intel) since then; pull requests welcome! -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
