From: Zhongliang Shu <zshu11@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK2.1 VF and NIC X552 PF - ixgbe SRIOV works?
Date: Tue, 3 Nov 2015 23:06:40 +0000 (UTC) [thread overview]
Message-ID: <1986782785.1874136.1446592000552.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <1986782785.1874136.1446592000552.JavaMail.yahoo@mail.yahoo.com>
Hi, Guys:
I have developed a VM to use SRIOV VF of DPDK2.1 libraryand its PF NIC is interl X552 NIC. The VM is deployed on KVM on Linux box.
NIC Inforoot@localhost:~# modinfo ixgbe
filename: /lib/modules/3.14.49-rt46-WR7.0.0.5_ovp/kernel/drivers/juniper/x552-nic/ixgbe.ko
version: 4.2.0.4.1-unreleased
license: GPL
description: Intel(R) 10 Gigabit PCI Express Network Driver
Linux Box InfoLinux localhost 3.14.49-rt46-WR7.0.0.5_ovp #1 SMP PREEMPT RT Mon Oct 26 12:24:18 PDT 2015 x86_64 GNU/Linux
When the VM start, and its correct corresponding MAC is pushed into PF.
4: sxe0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master eth1br state UP mode DEFAULT group default qlen 1000
link/ether 88:a2:5e:09:bd:c1 brd ff:ff:ff:ff:ff:ff
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 2 MAC 52:54:00:ba:fa:f7, spoof checking on, link-state auto
vf 3 MAC 52:54:00:ee:e6:0d, spoof checking on, link-state auto
Linux Host dmesg:root@localhost:/lib# dmesg
[62995.451770] pci-stub 0000:03:10.4: claimed by stub
[62995.465783] ixgbe 0000:03:00.0: setting MAC 52:54:00:ba:fa:f7 on VF 2
[62995.465785] ixgbe 0000:03:00.0: Reload the VF driver to make this change effective.
[62995.520671] device vnet4 entered promiscuous mode
[62995.520900] eth0br: port 4(vnet4) entered forwarding state
[62995.520911] eth0br: port 4(vnet4) entered forwarding state
[62995.666671] pci-stub 0000:03:10.4: enabling device (0000 -> 0002)
[62998.148072] pci-stub 0000:03:10.4: kvm assign device
[63010.548139] eth0br: port 4(vnet4) entered forwarding state
[63050.387806] pci-stub 0000:03:10.4: irq 97 for MSI/MSI-X
[63050.399811] pci-stub 0000:03:10.4: irq 97 for MSI/MSI-X
[63289.573419] ixgbe 0000:03:00.0 sxe0: VF Reset msg received from vf 2
[63290.033229] ixgbe 0000:03:00.0 sxe0: VF Reset msg received from vf 2
[63953.063867] ixgbe 0000:03:00.0: Malicious event on VF 2 tx:100000 rx:0
Several questions about the log msgs
1): its keep to see the log msgs: [63289.573419] ixgbe 0000:03:00.0 sxe0: VF Reset msg received from vf 2
[63290.033229] ixgbe 0000:03:00.0 sxe0: VF Reset msg received from vf 2 what reason cause these msg?
2): When try ping from the VM, it fails and there has msg:
[63953.063867] ixgbe 0000:03:00.0: Malicious event on VF 2 tx:100000 rx:0
what reason causes this msg?
3): Does DPDK2.1 VF and X552 PF is tested and supported?
By the way, the SRIOV of this VM work fine for X550 NIC and 82580 NIC,
Thanks.
next parent reply other threads:[~2015-11-03 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 23:06 Zhongliang Shu [this message]
2015-11-04 2:13 ` Lu, Wenzhuo
2015-11-07 6:03 ` Zhongliang Shu
2015-11-09 2:09 ` Lu, Wenzhuo
2015-11-11 6:47 ` Lu, Wenzhuo
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=1986782785.1874136.1446592000552.JavaMail.yahoo@mail.yahoo.com \
--to=zshu11@yahoo.com \
--cc=dev@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).