From: Declan Doherty <declan.doherty@intel.com>
To: Xuelin Shi <xuelin.shi@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] example/l2fwd-crypto: maybe an issue?
Date: Mon, 27 Jun 2016 09:44:48 +0100 [thread overview]
Message-ID: <40f77853-9eb3-31b6-1149-b64e0fe06360@intel.com> (raw)
In-Reply-To: <AM2PR04MB08490E72D59A4FDDC46CCF3E8C2D0@AM2PR04MB0849.eurprd04.prod.outlook.com>
On 23/06/16 06:30, Xuelin Shi wrote:
> Hi,
>
> Do we have assumption each core will have a separate crypto device?
>
> I have only one crypto device with several queues which are shared by multi-cores.
>
> As I run the l2fwd-crypto, only one cparam is valid and has a good dev_id.
> The other cparam is crashing.
>
> The reason is the other qconf assoicated with the core is not initializing the dev_id
> since only one crypto device is available.
>
> Thanks,
> Forrest
>
Hey Forrest, yes we made the assumption of one device per core the
application, we just default to using queue pair 0 of each crypto
device. It shouldn't be to much work to modify the main() and
initialize_cryptodevs() to instead allocate a cryptodev and queue pair
to each set of cparams. If you are using software crypto PMDs such as
the AESNI_MB PMD the simplest approach is just to create multiple
devices using the EAL options.
Regards
Declan
prev parent reply other threads:[~2016-06-27 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 5:30 Xuelin Shi
2016-06-27 8:44 ` Declan Doherty [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=40f77853-9eb3-31b6-1149-b64e0fe06360@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=xuelin.shi@nxp.com \
/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).