From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "zbigniew.bodek@caviumnetworks.com"
<zbigniew.bodek@caviumnetworks.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] test/crypto: create only one virtual device if needed
Date: Tue, 18 Apr 2017 11:41:15 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974780BA2F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1492515579-130563-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Tuesday, April 18, 2017 12:40 PM
> To: dev@dpdk.org
> Cc: zbigniew.bodek@caviumnetworks.com;
> jerin.jacob@caviumnetworks.com; Doherty, Declan; De Lara Guarch, Pablo
> Subject: [PATCH 1/2] test/crypto: create only one virtual device if needed
>
> Instead of creating two virtual devices per PMD, if they have not
> been initialized from EAL already, create only one, as only the
> first device is used for the crypto tests.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
I have tested this change on all PMDs but ARMv8, but I assume that it will work well.
Let me know if you see any issues.
Thanks,
Pablo
next prev parent reply other threads:[~2017-04-18 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 11:39 Pablo de Lara
2017-04-18 11:39 ` [dpdk-dev] [PATCH 2/2] test/crypto: create unique driver name Pablo de Lara
2017-04-18 13:12 ` Zhang, Roy Fan
2017-04-18 15:46 ` De Lara Guarch, Pablo
2017-04-18 11:41 ` De Lara Guarch, Pablo [this message]
2017-04-18 15:46 ` [dpdk-dev] [PATCH 1/2] test/crypto: create only one virtual device if needed De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D8974780BA2F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=zbigniew.bodek@caviumnetworks.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).