From: "Roberts, Lee A." <lee.roberts@hp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] testpmd link status reporting for ixgbevf_pmd
Date: Thu, 30 Oct 2014 19:31:45 +0000 [thread overview]
Message-ID: <D64EC45690EF85409BA6C4730E0162244E984083@G4W3231.americas.hpqcorp.net> (raw)
Hello,
I am running "testpmd" in DPDK 1.7.1, using two ixgbevf devices in my host OS.
I am finding that "testpmd" reports link status with speed 100 Mbps and half-duplex:
# $RTE_SDK/$RTE_TARGET/app/testpmd -c f -n 4 -- -i
...
EAL: PCI device 0000:03:10.2 on NUMA socket 0
EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
EAL: 0000:03:10.2 not managed by VFIO driver, skipping
EAL: PCI memory mapped at 0x7f482b1ee000
EAL: PCI memory mapped at 0x7f482b1ea000
EAL: PCI device 0000:03:10.3 on NUMA socket 0
EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
EAL: 0000:03:10.3 not managed by VFIO driver, skipping
EAL: PCI memory mapped at 0x7f482b1e6000
EAL: PCI memory mapped at 0x7f482b196000
...
Interactive-mode selected
Configuring Port 0 (socket 0)
Port 0: 3E:1D:AD:A9:3B:E6
Configuring Port 1 (socket 0)
Port 1: 6E:55:5D:14:4A:06
Checking link statuses...
Port 0 Link Up - speed 100 Mbps - half-duplex
Port 1 Link Up - speed 100 Mbps - half-duplex
Done
testpmd> show port info all
********************* Infos for port 0 *********************
MAC address: 3E:1D:AD:A9:3B:E6
Connect to socket: 0
memory allocation on the socket: 0
Link status: up
Link speed: 100 Mbps
Link duplex: half-duplex
Promiscuous mode: disabled
Allmulticast mode: disabled
Maximum number of MAC addresses: 128
Maximum number of MAC addresses of hash filtering: 4096
VLAN offload:
strip on
filter on
qinq(extend) off
********************* Infos for port 1 *********************
MAC address: 6E:55:5D:14:4A:06
Connect to socket: 0
memory allocation on the socket: 0
Link status: up
Link speed: 100 Mbps
Link duplex: half-duplex
Promiscuous mode: disabled
Allmulticast mode: disabled
Maximum number of MAC addresses: 128
Maximum number of MAC addresses of hash filtering: 4096
VLAN offload:
strip on
filter on
qinq(extend) off
testpmd>
I have checked that underlying devices are configured up. Before binding the virtual functions
to igb_uio, ethtool shows the expected speed and duplex settings:
# ethtool enp3s16f2
Settings for enp3s16f2:
Supported ports: [ ]
Supported link modes: 10000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: Unknown!
Auto-negotiation: off
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
#
I see similar results if I bind the virtual functions to vfio-pci.
I have also tested the top-of-tree DPDK and see the same results.
Under an older DPDK 1.5.1r1, "testpmd" reports the speed as 10000 Mbps and full-duplex.
Has anyone else seen this? Suggestions?
- Lee Roberts
reply other threads:[~2014-10-30 19: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=D64EC45690EF85409BA6C4730E0162244E984083@G4W3231.americas.hpqcorp.net \
--to=lee.roberts@hp.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).