pcp
[Top] [All Lists]

[Bug 1067] linux pmda does too much work for network.interface queries

To: pcp@xxxxxxxxxxx
Subject: [Bug 1067] linux pmda does too much work for network.interface queries
From: bugzilla-daemon@xxxxxxxxxxx
Date: Fri, 01 May 2015 17:30:29 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <bug-1067-835@xxxxxxxxxxxxxxxx/bugzilla/>
References: <bug-1067-835@xxxxxxxxxxxxxxxx/bugzilla/>

Comment # 14 on bug 1067 from
Michele,

This a physical system set up to run plugged to several isolated networks for
KVM VMs and other services (e.g. a compute node for OpenStack instances, with
private and public network access, etc).

Each of those network devices are physical NICs ports, the p#p# network devices
are PCI NICs (some 1Gb, some 10Gb), and the em# network devices are on-board
NICs.

For the 10Gb NICs, here's the ethtool output:

# ethtool -i p4p2
driver: ixgbe
version: 3.15.1-k
firmware-version: 0x546c0001
bus-info: 0000:42:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

and for the 1Gb NIC,

# ethtool -i p7p1
driver: igb
version: 5.0.5-k
firmware-version: 1.67, 0x80000ba6, 15.0.28
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

One interesting, and perhaps useful fact, is that the network device p4p2 is
actually DOWN which is probably why is not populating /sys/class/net/p4p2/speed

Thanks for your help.


You are receiving this mail because:
  • You are on the CC list for the bug.
<Prev in Thread] Current Thread [Next in Thread>