From: Mats Liljegren <liljegren.mats2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Issues with multiple DPDK instances
Date: Thu, 27 Feb 2014 15:30:29 +0100 [thread overview]
Message-ID: <CA+xJJ18G05HFOvSw0rvu+M6q5096CLmvYtE-h4UZ0s8fwt24CA@mail.gmail.com> (raw)
I'm trying to get multiple DPDK instances (processes) but seems to
have problems with getting the multiple queues that this (as far as I
understand it) requires.
I'm using the following command line for the host:
sudo insmod igb max_vfs=0,1,1,0 VMDQ=0,2,2,0
The idea here is that first and last interface will be kept on host,
while the two middle interfaces will be given to guest as virtual
functions.
When starting the primary, it fails saying "-22" in call to
rte_eth_dev_configure(), which means EINVAL. I have noticed that if I
set 1 queue for rx and tx, it starts. But setting 2 queues for rx and
tx respectively, it fails.
Am I using the wrong parameters to IGB?
Best regards
Mats Liljegren
reply other threads:[~2014-02-27 14:30 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=CA+xJJ18G05HFOvSw0rvu+M6q5096CLmvYtE-h4UZ0s8fwt24CA@mail.gmail.com \
--to=liljegren.mats2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).