Jason Lee

@masterleinad Fixed

> Can you call into our weekly meeting on Wednesday so we can discuss the above mentioned questions? We may need to get Galen and Geoff involved too. I am...

@nwf I should have worded that better. The only data that diverges from ZFS are abd payloads. I intentionally did not deallocate `zio->io_abd` and `rc->rc_abd` to 1. Reuse existing data...

@tonyhutter The software provider/kernel offloader is included with this pull request because it links with ZFS and reuses ZFS functions instead of implementing its own operations. The software provider can...

> I think the whole idea is that dpusm should be implementing its own operations, since it's an external module. That's why ZFS would want to call it - because...

@Ornias1993 Can you elaborate on the QAT issues you have experienced? In theory, ZFS should work with or without Z.I.A. enabled (perhaps the ifguards can be removed when Z.I.A. is...

@Ornias1993 The configuration can be changed to always try to find dpusm symbols (allowing for it not to be found) and the include guards can be removed so that Z.I.A....

@sempervictus The weak pointer check is done at initialization and finalization. The functions are only defined if they were available at ZFS module load time. https://github.com/openzfs/zfs/blob/73adbe60b1b988342d29ed634e24c5088a31202b/module/zfs/zia.c#L220-L229 Testing of providers by...

I do long multiplication in [`uint128_t`](https://github.com/calccrypto/uint128_t/blob/master/uint128_t.cpp#L208) and [`uint256_t`](https://github.com/calccrypto/uint256_t/blob/master/uint256_t.cpp#L317) because these two types have fixed numbers of internal digits, and thus multiplication can be done in constant time. [I have implemented...

Cool! Thanks! I'll get to it at some point.