Re: Removing crypto(9) "opencrypto" and /dev/crypto

Michael Neumann <[email protected]> Sun, 10 Aug 2025 16:04:10 +0200
Newsgroups gmane.os.dragonfly-bsd.user,gmane.os.dragonfly-bsd.kernel
Message-ID <[email protected]>
On Sun, Aug 10, 2025 at 03:38:36PM +0200, Michael Neumann wrote:
> On Sun, Aug 10, 2025 at 09:59:44AM +0800, Aaron LI wrote:
> > On 8/8/25 6:20 PM, Michael Neumann wrote:
> > > Hi,
> > 
> > Hi Michael,
> > 
> > Great job!
> 
> Hi Aaron,
> 
> 
> > > I'd like to commit the following two patches, removing a lot of "bloat":
> > > 
> > > https://leaf.dragonflybsd.org/~mneumann/0001-crypto-remove-dev-crypto-pseudo-device.patch
> > 
> > Some suggestions:
> > 
> > 1. UPDATING:
> >    As we're removing 'device cryptodev' from the default kernel config, I
> > suggest we first make 'cryptdev' a no-op and then remove it in a later
> > release.  The UPDATING file said similar notes for the FFS_ROOT option.
> 
> Thanks for the notice! I am trying to accomplish that with a line
> in sys/conf/files like:
> 
> 	NOOP     optional cryptodev no-obj \
> 		 warning "device cryptodev removed"
> 
> And the same for the other removed devices like "aesni", "safe", etc.

Removing "device aesni" isn't that easy as it is still used to compile
in the aesni code. I'd like to replace that with "options AESNI", but
not sure if this would "clash".

In addition to that, the assembly instructions for AESNI ideally
would be moved under cpu/x86_x86 and also enabled in VKERNEL.

Regards,

  Michael