From: Dirk-Holger Lenz <dirk.lenz@ng4t.com>
To: users@dpdk.org
Subject: [dpdk-users] cannot allocate more than one vdev device of a type
Date: Thu, 3 Aug 2017 15:45:39 +0200 [thread overview]
Message-ID: <933d585b-6e5e-f032-040f-2f99bab733ff@ng4t.com> (raw)
it is not possible to allocate more than one vdev of a type
(e.g. crypto_openssl or crypto_aesni_mb).
Our application may use several crypto devices which may
be virtual devices.
In the past it was possible to have several arguments of
--vdev (as much as devices needed)
(e.g. --vdev=crypto_openssl) given to rte_eal_init().
In the current version (17.08rc3) in any case only one device
is allocated.
In our case we are using dpdk built as shared libraries.
This happens due to the check in vdev_scan():
dev = find_vdev(devargs->name);
if (dev)
continue;
and in rte_cryptodev_pmd_allocate()
if (rte_cryptodev_pmd_get_named_dev(name) != NULL) {
CDEV_LOG_ERR("Crypto device with name %s already "
"allocated!", name);
return NULL;
}
next reply other threads:[~2017-08-03 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 13:45 Dirk-Holger Lenz [this message]
2017-08-03 13:57 ` De Lara Guarch, Pablo
2017-08-03 14:09 ` Dirk-Holger Lenz
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=933d585b-6e5e-f032-040f-2f99bab733ff@ng4t.com \
--to=dirk.lenz@ng4t.com \
--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).