On Mon, 2017-05-29 at 15:35 +0100, Sergio Gonzalez Monroy wrote:
> Hi,
> 
> I have not seen that behavior before.
> 
> The dpdk_crypto_sw is only for enabling SW crypto, the default is to 
> support just HW crypto devices.
> 
> I cannot think of a reason why you would see that behavior.
> Basically we just check if we found enough DPDK/Cryptodev HW crypto 
> devices for the number of workers configured.
> How have you pin point the wait/stall to the Cryptodev initialization?
I haven't spent much time on it however this wasn't happening on the previous
release (17.02) I used for my VSPerf environment. I then noticed this new
"message" and thought to raise the question here.

If you do not see the issue and believe that cannot cause this bootstrap problem
then it must be something else. I will dig further but my environment hasn't
changed beside the new VPP version.

> 
> Thanks,
> Sergio
> 
> On 29/05/2017 15:27, Marco Varlese wrote:
> > 
> > Hi all,
> > 
> > I pulled the latest code from master branch last week and I'm seeing
> > something
> > new and related (possibly) to the Cryptodev support in VPP/DPDK.
> > 
> > The issue is that it now takes much longer for VPP to initialize...
> > eventually
> > printing out the message:
> > "not enough Cryptodevs, default to OpenSSL IPsec"
> > 
> > I'm building the code - as before - by:
> > > 
> > > make bootstrap
> > > make build-release
> > which produced a config file with the dpdk-crypto-sw disabled (see below).
> > [   45s] with:
> > [   45s]   dpdk_crypto_sw          no
> > 
> > I wonder if anybody is experiencing the same behaviour (I found it out
> > thanks to
> > VSPerf which was going in timeout because of VPP)?
> > 
> > Is this something which we can disable in VPP (although from the configure
> > it
> > should already be disabled)? It looks strange to me that although the
> > feature is
> > disabled, the code is still looking for crypto-devs via the DPDK
> > infrastructure.
> > 
> > Any thoughts?
> > 
> > 
> > Regards,
> > Marco
> > 
> > _______________________________________________
> > vpp-dev mailing list
> > [email protected]
> > https://lists.fd.io/mailman/listinfo/vpp-dev
> 
> 
> 
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to