RE: Unable to receive multicast packet on VF
> -Original Message- > From: Skidmore, Donald C [mailto:donald.c.skidm...@intel.com] > Sent: Saturday, March 29, 2014 5:54 AM > To: Komatsubara Madoka(小松原 円); linux-kernel@vger.kernel.org; > e1000-de...@lists.sourceforge.net; net...@vger.kernel.org > Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) > Subject: RE: Unable to receive multicast packet on VF > > > > > -Original Message- > > From: Madoka Komatsubara [mailto:m-komatsub...@ab.jp.nec.com] > > Sent: Friday, March 28, 2014 4:49 AM > > To: linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net; > > net...@vger.kernel.org > > Cc: Hiroshi Shimamoto; Hiroshi Baba > > Subject: [E1000-devel] Unable to receive multicast packet on VF > > > > Hi all, > > > > > > We would like to use multicast packet on the guest with Intel 82599EB > > SR- IOV. > > However, the document says that adding the multicast MAC address to > > the VF is allowed during PF initialization only. (Please refer to the > > URL below.) It means that we couldn't handle dynamically allocated multicast > address. > > > > On the other hand, > > >From the data sheet, 82599EB has Multicast Promiscuous mode. > > We could enable it on PF and all multicast packets are delivered to every > VF. > > That doesn't seem good, because each guest has to handle unnecessary > > packet. > > > > Isn't it good to have a feature to add specific multicast address to VF? > > Does anyone know that issue or the solution? > > > > > > > > <http://www.intel.com/content/dam/www/public/us/en/documents/datas > > heets/82599-10-gbe-controller-datasheet.pdf> > > page585 > > section 8.2.3.7.7 > > "This table should be initialized by software before transmit and > > receive are enabled." > > > > Regards, > > Madoka Komatsubara > > > > Hi Madoka, > > You can see where we are changing the multicast address list in the VF driver > in ixgbevf_set_rx_mode(). This not only called via ndo_set_rx_mode but in > our up and open calls. So while it is true this needs to be initialized > before > transmit and receive are enabled, the value can be changed without requiring > the module to be reloaded. > > Hope that helps, > -Don Hi Donald, Thank you for your information. it is currently under consideration. I will contact you again later. Regards, Madoka Komatsubara -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: fail to add 64 VLANs or more when SR-IOV is enabled
>-Original Message- >From: Komatsubara Madoka(小松原 円) >Sent: Thursday, March 27, 2014 6:11 PM >To: 'linux-kernel@vger.kernel.org'; 'e1000-de...@lists.sourceforge.net'; >'net...@vger.kernel.org' >Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) >Subject: fail to add 64 VLANs or more when SR-IOV is enabled > >Hi all, > > >We're facing an issue that we cannot add 64 VLANs or more per VF. >When using SR-IOV, pass through a VF to the KVM guest and a lot of VLANs, we >could add 63 VLANs using vconfig but we >failed to add 64th VLAN. >We'd like to use many VLANs on the guest with SR-IOV. >We're using Intel's 82599EB chip with ixgbe and ixgbevf driver. > >Has anyone seen the same issue? >Is there any idea to solve this? > Hi Donald, Do you also notice this problem? We're facing an issue that we can use only 64 VLANs per VF. We're using Intel's 82599EB chip with ixgbe and ixgbevf driver. Is it subject to the specification restrictions only 64 VLAN can use per VF? We'd like to use about 2000 VLAN per VF. Does it come from hardware? Regards, Madoka Komatsubara >The below instruction is a reproducing method. >Create hundred VLANs on the guest. > ># for i in `seq 100 199`; do vconfig add eth2 $i; ifconfig 192.168.$i.1/24; >done > ># vconfig add eth2 100 >Added VLAN with VID == 100 to IF -:eth2:- > ># vconfig add eth2 101 >Added VLAN with VID == 101 to IF -:eth2:- > ># vconfig add eth2 102 >Added VLAN with VID == 102 to IF -:eth2:- > >... > ># vconfig add eth2 162 >Added VLAN with VID == 162 to IF -:eth2:- > ># vconfig add eth2 163 >ERROR: trying to add VLAN #163 to IF -:eth2:- error: Permission denied >SIOCSIFADDR: No such device >eth2.163: unknown interface: No such device > ># vconfig add eth2 164 >ERROR: trying to add VLAN #164 to IF -:eth2:- error: Permission denied >SIOCSIFADDR: No such device >eth2.164: unknown interface: No such device > ># vconfig add eth2 165 >ERROR: trying to add VLAN #165 to IF -:eth2:- error: Permission denied >SIOCSIFADDR: No such device >eth2.165: unknown interface: No such device > > >thanks, >Madoka Komatsubara -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [E1000-devel] fail to add 64 VLANs or more when SR-IOV is enabled
> -Original Message- > From: Fujinaka, Todd [mailto:todd.fujin...@intel.com] > Sent: Thursday, April 03, 2014 8:23 AM > To: Komatsubara Madoka(小松原 円); Skidmore, Donald C; > linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net; > net...@vger.kernel.org > Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) > Subject: RE: [E1000-devel] fail to add 64 VLANs or more when SR-IOV is enabled > > I think you're running into the filter limit for VFs. > Hi Todd, Thank you for the quick response. How can I increase the limit？ Regards, Madoka Komatsubara > Todd Fujinaka > Software Application Engineer > Networking Division (ND) > Intel Corporation > todd.fujin...@intel.com > (503) 712-4565 > > > -Original Message- > From: Madoka Komatsubara [mailto:m-komatsub...@ab.jp.nec.com] > Sent: Wednesday, April 02, 2014 2:11 AM > To: Skidmore, Donald C; linux-kernel@vger.kernel.org; > e1000-de...@lists.sourceforge.net; net...@vger.kernel.org > Cc: Hiroshi Shimamoto; Hiroshi Baba > Subject: Re: [E1000-devel] fail to add 64 VLANs or more when SR-IOV is enabled > > > >-Original Message- > >From: Komatsubara Madoka(小松原 円) > >Sent: Thursday, March 27, 2014 6:11 PM > >To: 'linux-kernel@vger.kernel.org'; 'e1000-de...@lists.sourceforge.net'; > 'net...@vger.kernel.org' > >Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) > >Subject: fail to add 64 VLANs or more when SR-IOV is enabled > > > >Hi all, > > > > > >We're facing an issue that we cannot add 64 VLANs or more per VF. > >When using SR-IOV, pass through a VF to the KVM guest and a lot of VLANs, > we could add 63 VLANs using vconfig but we >failed to add 64th VLAN. > >We'd like to use many VLANs on the guest with SR-IOV. > >We're using Intel's 82599EB chip with ixgbe and ixgbevf driver. > > > >Has anyone seen the same issue? > >Is there any idea to solve this? > > > > Hi Donald, > > Do you also notice this problem? > We're facing an issue that we can use only 64 VLANs per VF. > We're using Intel's 82599EB chip with ixgbe and ixgbevf driver. > > > Is it subject to the specification restrictions only 64 VLAN can use per VF? > We'd like to use about 2000 VLAN per VF. > > Does it come from hardware? > > > > Regards, > Madoka Komatsubara > > > >The below instruction is a reproducing method. > >Create hundred VLANs on the guest. > > > ># for i in `seq 100 199`; do vconfig add eth2 $i; ifconfig 192.168.$i.1/24; > done > > > ># vconfig add eth2 100 > >Added VLAN with VID == 100 to IF -:eth2:- > > > ># vconfig add eth2 101 > >Added VLAN with VID == 101 to IF -:eth2:- > > > ># vconfig add eth2 102 > >Added VLAN with VID == 102 to IF -:eth2:- > > > >... > > > ># vconfig add eth2 162 > >Added VLAN with VID == 162 to IF -:eth2:- > > > ># vconfig add eth2 163 > >ERROR: trying to add VLAN #163 to IF -:eth2:- error: Permission denied > >SIOCSIFADDR: No such device > >eth2.163: unknown interface: No such device > > > ># vconfig add eth2 164 > >ERROR: trying to add VLAN #164 to IF -:eth2:- error: Permission denied > >SIOCSIFADDR: No such device > >eth2.164: unknown interface: No such device > > > ># vconfig add eth2 165 > >ERROR: trying to add VLAN #165 to IF -:eth2:- error: Permission denied > >SIOCSIFADDR: No such device > >eth2.165: unknown interface: No such device > > > > > >thanks, > >Madoka Komatsubara > > > - > - > ___ > E1000-devel mailing list > e1000-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [E1000-devel] fail to add 64 VLANs or more when SR-IOV is enabled
> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, April 03, 2014 10:40 AM > To: Komatsubara Madoka(小松原 円) > Cc: todd.fujin...@intel.com; donald.c.skidm...@intel.com; > linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net; > net...@vger.kernel.org; Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕 > 司) > Subject: Re: [E1000-devel] fail to add 64 VLANs or more when SR-IOV is enabled > > From: Madoka Komatsubara > Date: Thu, 3 Apr 2014 01:12:13 + > > > Thank you for the quick response. > > How can I increase the limit？ > > It's a hardware limit, you cannot increase it. Thank you for your information. Does it mean disabling filter is the only way to use over 64 VLANs and is it possible? Regards, Madoka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Unable to receive multicast packet on VF
> -Original Message- > From: Komatsubara Madoka(小松原 円) > Sent: Wednesday, April 02, 2014 6:05 PM > To: 'Skidmore, Donald C'; linux-kernel@vger.kernel.org; > e1000-de...@lists.sourceforge.net; net...@vger.kernel.org > Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) > Subject: RE: Unable to receive multicast packet on VF > > > > -Original Message- > > From: Skidmore, Donald C [mailto:donald.c.skidm...@intel.com] > > Sent: Saturday, March 29, 2014 5:54 AM > > To: Komatsubara Madoka(小松原 円); linux-kernel@vger.kernel.org; > > e1000-de...@lists.sourceforge.net; net...@vger.kernel.org > > Cc: Shimamoto Hiroshi(島本 裕志); Baba Hiroshi(馬場 裕司) > > Subject: RE: Unable to receive multicast packet on VF > > > > > > > > > -Original Message- > > > From: Madoka Komatsubara [mailto:m-komatsub...@ab.jp.nec.com] > > > Sent: Friday, March 28, 2014 4:49 AM > > > To: linux-kernel@vger.kernel.org; e1000-de...@lists.sourceforge.net; > > > net...@vger.kernel.org > > > Cc: Hiroshi Shimamoto; Hiroshi Baba > > > Subject: [E1000-devel] Unable to receive multicast packet on VF > > > > > > Hi all, > > > > > > > > > We would like to use multicast packet on the guest with Intel > > > 82599EB > > > SR- IOV. > > > However, the document says that adding the multicast MAC address to > > > the VF is allowed during PF initialization only. (Please refer to > > > the URL below.) It means that we couldn't handle dynamically > > > allocated multicast > > address. > > > > > > On the other hand, > > > >From the data sheet, 82599EB has Multicast Promiscuous mode. > > > We could enable it on PF and all multicast packets are delivered to > > > every > > VF. > > > That doesn't seem good, because each guest has to handle unnecessary > > > packet. > > > > > > Isn't it good to have a feature to add specific multicast address to VF? > > > Does anyone know that issue or the solution? > > > > > > > > > > > > <http://www.intel.com/content/dam/www/public/us/en/documents/datas > > > heets/82599-10-gbe-controller-datasheet.pdf> > > > page585 > > > section 8.2.3.7.7 > > > "This table should be initialized by software before transmit and > > > receive are enabled." > > > > > > Regards, > > > Madoka Komatsubara > > > > > > > Hi Madoka, > > > > You can see where we are changing the multicast address list in the VF > > driver in ixgbevf_set_rx_mode(). This not only called via ndo_set_rx_mode > but in > > our up and open calls. So while it is true this needs to be initialized > before > > transmit and receive are enabled, the value can be changed without > > requiring the module to be reloaded. > > > > Hope that helps, > > -Don > > > Hi Donald, > > Thank you for your information. > it is currently under consideration. > I will contact you again later. > > > Regards, > Madoka Komatsubara Hi Donald, I'm sorry for the delay in my response. We would like to clarify the limitation described in the datasheet. We confirmed if the multicast address list is updated in the VF driver with the instruction below. The scenario is that the guest on host1 has an address on network1 and communicate with host2, on the same time, the guest newly gets an address on network2 and begin to communicate with host3. The result was that we could add new IPv6 address on the VF and receive new multicast address packet. We can't understand exactly what the description section 8.2.3.7.7(page585) in the 82599 datasheet http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf "This table should be initialized by software before transmit and receive are enabled." Could you please tell us what "before transmit and receive are enabled" means? We would like to add new communication on keeping previous packet communication. And the result looks fine. Here is our test scenario Step1: o Guest on the host1 Guest# ifconfig eth1 add 3ffe:5::fe/64 This is registered to a multicast filter of guest. o Host2 Host2# ifconfig eth1 add 3ffe:5::fd/64 Host2# ping6 -c1 3ffe:5::fe Guest receives a packet for the multicast address. Step2: Next, we confirmed if the multicast address list is updated while pinging. We keep on pinging to the guest from the host2. o Host2 Host2# ping6 3ffe:5::fe After that, we add new IPv6 address on the VF.
fail to add 64 VLANs or more when SR-IOV is enabled
Hi all, We're facing an issue that we cannot add 64 VLANs or more per VF. When using SR-IOV, pass through a VF to the KVM guest and a lot of VLANs, we could add 63 VLANs using vconfig but we failed to add 64th VLAN. We'd like to use many VLANs on the guest with SR-IOV. We're using Intel's 82599EB chip with ixgbe and ixgbevf driver. Has anyone seen the same issue? Is there any idea to solve this? The below instruction is a reproducing method. Create hundred VLANs on the guest. # for i in `seq 100 199`; do vconfig add eth2 $i; ifconfig 192.168.$i.1/24; done # vconfig add eth2 100 Added VLAN with VID == 100 to IF -:eth2:- # vconfig add eth2 101 Added VLAN with VID == 101 to IF -:eth2:- # vconfig add eth2 102 Added VLAN with VID == 102 to IF -:eth2:- ... # vconfig add eth2 162 Added VLAN with VID == 162 to IF -:eth2:- # vconfig add eth2 163 ERROR: trying to add VLAN #163 to IF -:eth2:- error: Permission denied SIOCSIFADDR: No such device eth2.163: unknown interface: No such device # vconfig add eth2 164 ERROR: trying to add VLAN #164 to IF -:eth2:- error: Permission denied SIOCSIFADDR: No such device eth2.164: unknown interface: No such device # vconfig add eth2 165 ERROR: trying to add VLAN #165 to IF -:eth2:- error: Permission denied SIOCSIFADDR: No such device eth2.165: unknown interface: No such device thanks, Madoka Komatsubara -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Unable to receive multicast packet on VF
Hi all, We would like to use multicast packet on the guest with Intel 82599EB SR-IOV. However, the document says that adding the multicast MAC address to the VF is allowed during PF initialization only. (Please refer to the URL below.) It means that we couldn't handle dynamically allocated multicast address. On the other hand, >From the data sheet, 82599EB has Multicast Promiscuous mode. We could enable it on PF and all multicast packets are delivered to every VF. That doesn't seem good, because each guest has to handle unnecessary packet. Isn't it good to have a feature to add specific multicast address to VF? Does anyone know that issue or the solution? <http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf> page585 section 8.2.3.7.7 "This table should be initialized by software before transmit and receive are enabled." Regards, Madoka Komatsubara -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
