From: Or Gerlitz <ogerlitz@mellanox.com>
To: Greg Rose <gregory.v.rose@intel.com>
Cc: David Miller <davem@davemloft.net>,
Alexander Duyck <alexander.h.duyck@intel.com>,
netdev <netdev@vger.kernel.org>, Rony Efraim <ronye@mellanox.com>,
<Sibai.li@intel.com>
Subject: Re: getting VF link info seems to be broken in 3.9-rc8
Date: Wed, 24 Apr 2013 19:07:54 +0300 [thread overview]
Message-ID: <5178035A.5090306@mellanox.com> (raw)
In-Reply-To: <20130424090133.00005ca6@unknown>
On 24/04/2013 19:01, Greg Rose wrote:
> From our validation engineer Sibai Li (added to response):
>
> I tested 3.9.0-rc8, I have no problem to list vf info. But I didn’t run
> in FPP mode. But I don't think it's a matter. From the info he gave
> here, I didn’t see he loaded the vf driver when he ran in kernel
> 3.9.0-rc8, but he did load the driver in 3.8.8.
>
> ---------
>
> I'd add that having the VF driver loaded shouldn't make any difference.
I have tested again (this time the server is booted on net-next which
is 3.9-rc8+) and the VF driver IS loaded, but stillno sign for the VF in
the ip link show output
# lspci | grep Eth
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
05:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
05:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller
Virtual Function (rev 01)
05:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller
Virtual Function (rev 01)
# lsmod | grep ixgbe
ixgbevf 34062 0
ixgbe 150783 0
hwmon 1839 1 ixgbe
mdio 4263 1 ixgbe
ptp 8400 2 ixgbe,igb
dca 6822 3 ixgbe,igb,ioatdma
# /mnt/upstream/tools/iproute2/ip/ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0
state UP mode DEFAULT qlen 1000
link/ether 00:25:90:36:9c:ec brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:25:90:36:9c:ed brd ff:ff:ff:ff:ff:ff
10: eth11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:1b:21:55:1d:00 brd ff:ff:ff:ff:ff:ff
11: eth10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:1b:21:55:1d:01 brd ff:ff:ff:ff:ff:ff
12: eth22: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 3a:20:bd:09:ce:9d brd ff:ff:ff:ff:ff:ff
13: eth20: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 52:42:81:a7:6e:da brd ff:ff:ff:ff:ff:ff
14: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP mode DEFAULT
link/ether 00:25:90:36:9c:ec brd ff:ff:ff:ff:ff:ff
17: eth16: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN mode DEFAULT qlen 1000
link/ether 00:02:c9:e6:01:11 brd ff:ff:ff:ff:ff:ff
18: eth17: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN mode DEFAULT qlen 1000
link/ether 00:02:c9:e6:01:12 brd ff:ff:ff:ff:ff:ff
19: eth18: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:02:c9:e6:02:11 brd ff:ff:ff:ff:ff:ff
20: eth19: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:02:c9:e6:02:12 brd ff:ff:ff:ff:ff:ff
21: eth28: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:02:c9:e6:03:11 brd ff:ff:ff:ff:ff:ff
22: eth27: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT qlen 1000
link/ether 00:02:c9:e6:03:12 brd ff:ff:ff:ff:ff:ff
# pwd
/sys/class/net
# ls -l
total 0
lrwxrwxrwx 1 root root 0 Apr 24 18:44 br0 -> ../../devices/virtual/net/br0
lrwxrwxrwx 1 root root 0 Apr 24 18:44 eth0 ->
../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/net/eth0
lrwxrwxrwx 1 root root 0 Apr 24 18:44 eth1 ->
../../devices/pci0000:00/0000:00:01.0/0000:01:00.1/net/eth1
lrwxrwxrwx 1 root root 0 Apr 24 18:45 eth10 ->
../../devices/pci0000:00/0000:00:09.0/0000:05:00.1/net/eth10
lrwxrwxrwx 1 root root 0 Apr 24 18:45 eth11 ->
../../devices/pci0000:00/0000:00:09.0/0000:05:00.0/net/eth11
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth16 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.0/net/eth16
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth17 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.0/net/eth17
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth18 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.1/net/eth18
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth19 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.1/net/eth19
lrwxrwxrwx 1 root root 0 Apr 24 18:44 eth20 ->
../../devices/pci0000:00/0000:00:09.0/0000:05:10.1/net/eth20
lrwxrwxrwx 1 root root 0 Apr 24 18:44 eth22 ->
../../devices/pci0000:00/0000:00:09.0/0000:05:10.0/net/eth22
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth27 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.2/net/eth27
lrwxrwxrwx 1 root root 0 Apr 24 18:51 eth28 ->
../../devices/pci0000:00/0000:00:07.0/0000:04:00.2/net/eth28
lrwxrwxrwx 1 root root 0 Apr 24 18:44 lo -> ../../devices/virtual/net/lo
next prev parent reply other threads:[~2013-04-24 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 13:08 getting VF link info seems to be broken in 3.9-rc8 Or Gerlitz
2013-04-24 15:05 ` Williams, Mitch A
2013-04-25 18:29 ` Alexander Duyck
2013-04-25 19:24 ` David Miller
2013-04-25 20:20 ` Alexander Duyck
2013-04-25 20:25 ` David Miller
2013-04-25 20:36 ` Alexander Duyck
2013-04-25 20:45 ` Stephen Hemminger
2013-04-25 20:49 ` David Miller
2013-04-25 21:10 ` Alexander Duyck
2013-04-24 15:38 ` Greg Rose
2013-04-24 16:01 ` Greg Rose
2013-04-24 16:07 ` Or Gerlitz [this message]
2013-04-24 16:12 ` Li, Sibai
2013-04-24 16:08 ` Li, Sibai
2013-04-24 16:34 ` Or Gerlitz
2013-04-24 16:44 ` Li, Sibai
2013-04-24 16:45 ` Or Gerlitz
2013-04-24 16:48 ` Rose, Gregory V
2013-04-24 16:56 ` Li, Sibai
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=5178035A.5090306@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=Sibai.li@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ronye@mellanox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.