From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Eric Kuha <kuhax005@umn.edu>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] EAL: Unable to parse device 'crypto_openssl'
Date: Mon, 11 Nov 2019 10:11:46 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435A21A0EE6@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CAG1M=GBikAwQDyVNxTuYXXQeDkxbe41ZA09Fe=UQxGGi+LGmXw@mail.gmail.com>
Hi Eric,
Please post the full command line and the error you're getting.
Fiona
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Eric Kuha
> Sent: Sunday, November 10, 2019 7:29 PM
> To: users@dpdk.org
> Subject: [dpdk-users] EAL: Unable to parse device 'crypto_openssl'
>
> Hello,
>
> Trying to create a crypto device.
>
> CONFIG_RTE_LIBRTE_PMD_OPENSSL is set to y,
>
> and both cryptodev_openssl_autotest and cryptodev_null_autotest
> succeeded on all tests.
>
> Why else would it not parse the EAL command line argument?
>
> Thank you,
>
> Eric
prev parent reply other threads:[~2019-11-11 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 19:29 Eric Kuha
2019-11-11 10:11 ` Trahe, Fiona [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=348A99DA5F5B7549AA880327E580B435A21A0EE6@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=kuhax005@umn.edu \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).