[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A3A921390EAE4044940E99EBF13D97322426365E@FMSMSX104.amr.corp.intel.com>
Date: Wed, 24 Apr 2013 16:56:36 +0000
From: "Li, Sibai" <sibai.li@...el.com>
To: "Rose, Gregory V" <gregory.v.rose@...el.com>,
Or Gerlitz <ogerlitz@...lanox.com>
CC: David Miller <davem@...emloft.net>,
"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
netdev <netdev@...r.kernel.org>, Rony Efraim <ronye@...lanox.com>
Subject: RE: getting VF link info seems to be broken in 3.9-rc8
Ok I see what you sew now, RTNETLINK might be broken.
> -----Original Message-----
> From: Rose, Gregory V
> Sent: Wednesday, April 24, 2013 9:49 AM
> To: Li, Sibai; Or Gerlitz
> Cc: David Miller; Duyck, Alexander H; netdev; Rony Efraim
> Subject: RE: getting VF link info seems to be broken in 3.9-rc8
>
>
>
> > -----Original Message-----
> > From: Li, Sibai
> > Sent: Wednesday, April 24, 2013 9:44 AM
> > To: Or Gerlitz
> > Cc: Rose, Gregory V; David Miller; Duyck, Alexander H; netdev; Rony
> > Efraim
> > Subject: RE: getting VF link info seems to be broken in 3.9-rc8
> >
> > This means that the VF driver is loaded before the PF is loaded. Did
> > you reload the VF after the PF is loaded?
>
> Sibai,
>
> It should not matter whether the VF driver is loaded or not when listing the VFs
> using "ip link show".
>
> - Greg
>
> > > -----Original Message-----
> > > From: Or Gerlitz [mailto:ogerlitz@...lanox.com]
> > > Sent: Wednesday, April 24, 2013 9:35 AM
> > > To: Li, Sibai
> > > Cc: Rose, Gregory V; David Miller; Duyck, Alexander H; netdev; Rony
> > > Efraim
> > > Subject: Re: getting VF link info seems to be broken in 3.9-rc8
> > >
> > > 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
Powered by blists - more mailing lists