Bug 93
Summary: | crypto vdev create will reset the dev_started flag when one dpdk process has been up the crypto vdev | ||
---|---|---|---|
Product: | DPDK | Reporter: | jin, wenjing (wenjing.1.jin) |
Component: | cryptodev | Assignee: | Pablo de Lara (pablo.de.lara.guarch) |
Status: | CONFIRMED --- | ||
Severity: | major | CC: | ajit.khaparde, roy.fan.zhang, wenjing.1.jin |
Priority: | Normal | ||
Version: | 17.05 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
jin, wenjing
2018-09-28 11:35:23 CEST
Pablo, Can you please take a look? Thanks (In reply to Ajit Khaparde from comment #1) > Pablo, Can you please take a look? Thanks hi Pablo, would you please help to check this issue? (In reply to jin, wenjing from comment #2) > (In reply to Ajit Khaparde from comment #1) > > Pablo, Can you please take a look? Thanks > > hi Pablo, > would you please help to check this issue? A secondary process should never create the software Cryptodev with the same name as the one created in primary process. To distinguish they shall use different suffix such as "crypto_aesni_mb0" and "crypto_aesni_mb1" for each process. Indeed we need to provide a way to prevent such usage. I will look into it. (In reply to jin, wenjing from comment #2) > (In reply to Ajit Khaparde from comment #1) > > Pablo, Can you please take a look? Thanks > > hi Pablo, > would you please help to check this issue? Hi, I cannot reproduce this bug. Could you offer more details, including the commands you are using? |