Load cryptodev as a kernel module
Remove cryptodev from kernel and build it as a module
Add GUI components for loading cryptodev as a module, and upgrade code so users have it on upgrade since it was in-kernel before. Fixes #5976
Having both aesni and cryptodev loaded at the same time appears to only negatively impact performance, no gains, so at the moment there is no need to load them at the same time.
#6 Updated by Jim Pingle over 2 years ago
I just pushed a GUI change to add it in as a choice next to aesni. Testing revealed no benefit to having both aesni and cryptodev loaded together, so having an option for just one or the other is OK for the time being. It actually lowered performance instead of raising it.
I also added upgrade code so that the cryptodev module would be loaded for users upgrading from previous versions. Since it was in the kernel before, this seemed to be the best POLA-friendly course of action.
#7 Updated by Luke Hamburg over 2 years ago
Had to look up POLA :)
In case I wasn't the only one: