I am doing some performance testing with openssl on a VIA C7 processor that
has a build-in crypto engine.
Using a 4.9-beta (current) for this test a was
unable to get access to cryptodev.

In the current changelog I read that
userland access to cryptodev has been disabled.

So i tried to enable it again
by setting kern.usercrypto

$ sysctl kern.usercrypto
kern.usercrypto=0

$ sudo
sysctl kern.usercrypto=1
sysctl: kern.usercrypto: Invalid argument

I did
check also on 4.8-current dating back to JAN-2, same there.
Then I decided to
check with 4.8 release,
Not only is kern.usercrypto=1 the default, but I don't
get these strange errors using sysctl to disable it.

Is this a problem in
current or is there a reason that I am no longer able to sysctl
kern.usercrypto=1

Thanks.
Marco





 


 










 

Reply via email to