From: Saurabh Mishra <saurabh.globe@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDK mbuf pool in SR-IOV env and one RX/TX queue
Date: Thu, 21 Jan 2016 14:24:38 -0800 [thread overview]
Message-ID: <CAMnwyJ26hHNR9u1W9SOseS1mBKPqFNkcRShKK5NYPpXc-xK9_A@mail.gmail.com> (raw)
Hi,
Is it possible for two or more processes to share the same mbuf_pool in
SR-IOV with single rx/tx queue?
rte_pktmbuf_pool_create(mbuf_pool_name,
NB_MBUFS,
MBUF_CACHE_SIZE, 0,
RTE_MBUF_DEFAULT_BUF_SIZE,
rte_socket_id());
We have seen that it does not work. However, with PCI passthrough of whole
NIC, we can easily share same mbuf_pool with many processes.
What are the limitations with SR-IOV and DPDK? If we create one primary and
no secondary proc-type, then that seems to work with SR-IOV. However, the
moment we add a secondary process, rte_mempool_lookup() returns NULL.
Note that we see only 1 queue for rx and tx and multi-queue gets disabled
the moment we enable VFs.
[683877.050219] ixgbe 0000:06:00.0: *Multi*queue Disabled: Rx Queue count =
1, Tx Queue count = 1
[683879.799872] ixgbe 0000:06:00.1: *Multi*queue Disabled: Rx Queue count =
1, Tx Queue count = 1
The device is question is as follows:
06:00.0 *Ether*net controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
06:00.1 *Ether*net controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
06:10.0 *Ether*net controller: Intel Corporation 82599 *Ether*net
Controller Virtual Function (rev 01)
06:10.1 *Ether*net controller: Intel Corporation 82599 *Ether*net
Controller Virtual Function (rev 01)
06:10.2 *Ether*net controller: Intel Corporation 82599 *Ether*net
Controller Virtual Function (rev 01)
06:10.3 *Ether*net controller: Intel Corporation 82599 *Ether*net
Controller Virtual Function (rev 01)
Thanks,
/Saurabh
reply other threads:[~2016-01-21 22:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAMnwyJ26hHNR9u1W9SOseS1mBKPqFNkcRShKK5NYPpXc-xK9_A@mail.gmail.com \
--to=saurabh.globe@gmail.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).