From: Or Gerlitz <ogerlitz@mellanox.com>
To: "Li, Sibai" <sibai.li@intel.com>
Cc: "Rose, Gregory V" <gregory.v.rose@intel.com>,
David Miller <davem@davemloft.net>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
netdev <netdev@vger.kernel.org>, Rony Efraim <ronye@mellanox.com>
Subject: Re: getting VF link info seems to be broken in 3.9-rc8
Date: Wed, 24 Apr 2013 19:34:44 +0300 [thread overview]
Message-ID: <517809A4.3070001@mellanox.com> (raw)
In-Reply-To: <A3A921390EAE4044940E99EBF13D97322426359F@FMSMSX104.amr.corp.intel.com>
On 24/04/2013 19:08, Li, Sibai wrote:
> The vfs are listed, eth22/eth20. Just the mac address is different. Reload the vf driver to see if it corrects the thing.
Sure, the VF are listed as NICs of their own, what's isn't listed is the
VF info from the PF NIC link info, e.g here's the casewhere its working,
on kernel 3.8.8-- my problem isn't the MAC misalignment
8: eth11: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
DOWN mode DEFAULT qlen 1000
link/ether 00:1b:21:55:1d:00 brd ff:ff:ff:ff:ff:ff
vf 0 MAC 00:11:00:11:00:11, spoof checking on
9: eth10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
mode DORMANT qlen 1000
link/ether 00:1b:21:55:1d:01 brd ff:ff:ff:ff:ff:ff
vf 0 MAC 00:10:00:10:00:10, spoof checking on
next prev parent reply other threads:[~2013-04-24 16:34 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
2013-04-24 16:12 ` Li, Sibai
2013-04-24 16:08 ` Li, Sibai
2013-04-24 16:34 ` Or Gerlitz [this message]
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=517809A4.3070001@mellanox.com \
--to=ogerlitz@mellanox.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 \
--cc=sibai.li@intel.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.