| Sure, but that's been Greg KH's stance on pretty much every kernel module that has no chance of going upstream [1]. "Simple, get your kernel driver into the main kernel tree (remember we are talking about drivers released under a GPL-compatible license here, if your code doesn't fall under this category, good luck, you are on your own here, you leech)." Also in the post you are citing, the technical change makes no reference to ZFS [2] or implies that the motivation is to break out of tree modules. The upstream community simply doesn't even consider out of tree projects when making changes. Whether that's good or bad is another discussion, but I don't see anything that's specific to ZFS. I should also note that to my knowledge, OpenZFS (formerly ZoL) was the only (open source) ZFS implementation that utilized vectorized checksums. At the very least FreeBSD's in-tree ZFS did not have vectorized checksums, as that was listed as one of the features FreeBSD would gain by moving to OpenZFS [3]. So the cited change didn't break ZFS, it just meant those checksums weren't as fast as they used to be. [1] https://www.kernel.org/doc/Documentation/process/stable-api-... [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... [3] https://lists.freebsd.org/pipermail/freebsd-current/2018-Dec... |
Man i just love that warm, lovely atmosphere in that project..and thats not even the leader....ahem sorry dictator (and he is even proud of that)