From: <cheng.luo.nq-FCd8Q96Dh0JBDgjK7y7TUQ@public.gmane.org>
To: <dev-VfR2kkLFssw@public.gmane.org>
Subject: DPDK failed to handle intialize VF
Date: Tue, 12 Nov 2013 16:12:16 +0900 [thread overview]
Message-ID: <XNM7$4$0$4$$1$2$9$A$9000061U5281d4b3@hitachi.com> (raw)
Hi,
I am using DPDK for SRIOV.
I have one Intel X520 with two PFs.
After binding the two PFs to igb_uio, I create two VFs and assign
them to a virtual machine.
I found that to wake up VF, the VF will send some message to PF
such as IXGBE_VF_SET_MACVLAN(0x06) and IXGBE_VF_API_NEGOTIATE(0x08)
for the initialization.
However, DPDK's PMD driver does not handle this messgae.
In the source code /lib/librte_pmd_ixgbe/ixgbe_pf.c
the function ixgbe_rcv_msg_from_vf only handle the following message:
IXGBE_VF_SET_MAC_ADDR (0x02)
IXGBE_VF_SET_MULTICAST (0x03)
IXGBE_VF_SET_LPE (0x04)
IXGBE_VF_SET_VLAN (0x05)
and take other message as error message and take no operation.
Therefore, if take DPDK to control the PF, I can not use VF with
ixgbevf driver in the VMs.
The PMD driver will endless print error message as follow:
-------------
PMD: Unhandled Msg 00000006
PMD: Unhandled Msg 00000008
-----------
And in the VMs, it also prints endless error message
---------------------
[ 447.339765] ixgbevf: eth1: ixgbevf_watchdog_task: NIC Link is Up, 10 Gbps
[ 447.748556] ixgbevf: eth1: ixgbevf_watchdog_task: NIC Link is Up, 10 Gbps
[ 447.844914] ixgbevf: eth1: ixgbevf_watchdog_task: NIC Link is Up, 10 Gbps
--------------------
While I also read the code in ixgbe, and found that it can handle message 0x06 and 0x08.
Is this a bug for DPDK ?
Or any step is wrong for my configuration?
I think DPDK should be ok to run in the host while with VF in the VM uses normal driver such as ixgbevf.
reply other threads:[~2013-11-12 7:12 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='XNM7$4$0$4$$1$2$9$A$9000061U5281d4b3@hitachi.com' \
--to=cheng.luo.nq-fcd8q96dh0jbdgjk7y7tuq@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).