Bug #5976
closed
Load cryptodev as a kernel module
100%
Description
Remove cryptodev from kernel and build it as a module
Updated by Chris Buechler about 8 years ago
- Target version changed from 2.3.1 to 2.3.2
Updated by Chris Buechler almost 8 years ago
- Target version changed from 2.3.2 to 2.4.0
Updated by Renato Botelho over 7 years ago
- Status changed from New to Rejected
IPsec is builtin GENERIC kernel even in FreeBSD and it depends of crypto. This change doesn't make sense anymore
Updated by Renato Botelho over 7 years ago
- Status changed from Rejected to Assigned
reopening since crypto is not cryptodev. Pointy hat to me
Updated by Renato Botelho about 7 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Applied in changeset 69860ee4f5ff9f1e5b87bc6fdcb6dfea66062726.
Updated by Jim Pingle about 7 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.
Updated by → luckman212 about 7 years ago
Had to look up POLA :)
In case I wasn't the only one:
https://en.m.wikipedia.org/wiki/Principle_of_least_astonishment
Updated by Jim Pingle about 7 years ago
- Status changed from Feedback to Resolved
Works as expected. Upgrading users that did not have aesni enabled will have cryptodev loaded on upgrade or with a new install.