Re: [E1000-devel] VFS vs MTU

2012-01-30 Thread Steve O'Brien
Greg,

Thanks for the reply.

Steve

-Original Message-
From: Rose, Gregory V [mailto:gregory.v.r...@intel.com] 
Sent: Monday, January 30, 2012 12:59 PM
To: Steve O'Brien; e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] VFS vs MTU

> -Original Message-
> From: Steve O'Brien [mailto:obr...@velocent.com]
> Sent: Monday, January 30, 2012 10:05 AM
> To: e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel] VFS vs MTU
> 
> 
> Has anyone else encountered this problem?
> 
> Sorry, my contact info is:
>   Steve O'Brien
>   obr...@velocent.com
>   Sr. Engineer
>   Velocent Systems

If the Intel 10Gig device you're is based on the 82599 controller then there
is an errata on that device that prevents use of jumbo frames while in
SR-IOV mode.  You must disable SR-IOV if you want to use jumbo frames.

The driver will not allow any parameter larger than 1500 for those devices
when SR-IOV mode is enabled and that is why you are getting the invalid
parameter error message.

The errata will be fixed in future generations of Intel 10gig controllers.
I apologize for the inconvenience.

- Greg

> 
> -Original Message-
> From: Steve O'Brien [mailto:obr...@velocent.com]
> Sent: Thursday, January 26, 2012 1:00 PM
> To: 'e1000-devel@lists.sourceforge.net'
> Subject: VFS vs MTU
> 
> 
> Oh, I hope this isn't a dumb question, but I can't set the MTU to 4096 
> using SR-IOV.
> 
> I'm using the X520-SR2 dual 82599 NIC with RedHat 6.0. I use 'modprobe 
> ixgbe max_vfs=4,4`, then try to increase the MTU using 'ifconfig eth2 
> mtu 4096', gives me the response `SIOCSIFMTU: Invalid argument`.
> 
> The modprobe appears successful, dmesg is:
> 
> Intel(R) 10 Gigabit PCI Express Network Driver - version 3.7.17-NAPI 
> Copyright (c) 1999-2011 Intel Corporation.
> ixgbe :13:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ixgbe
> :13:00.0: setting latency timer to 64
> ixgbe: I/O Virtualization (IOV) set to 4
> ixgbe: :13:00.0: ixgbe_check_options: FCoE Offload feature 
> disabled ixgbe :13:00.0: irq 28 for MSI/MSI-X ixgbe :13:00.0: 
> irq 29 for MSI/MSI-X ixgbe :13:00.0: (PCI Express:2.5GT/s:Width 
> x8)
> 00:1b:21:8e:ae:e4 ixgbe :13:00.0: eth2: MAC: 2, PHY: 15, SFP+: 5, 
> PBA
> No: E68785-003 ixgbe :13:00.0: eth2: Enabled Features: RxQ: 1 TxQ: 
> 1 LRO ixgbe :13:00.0: eth2: IOV: VF 0 is enabled mac 
> 36:25:DD:F1:C6:DC ixgbe :13:00.0: eth2: IOV: VF 1 is enabled mac 
> 3A:98:30:1A:89:9D ixgbe
> :13:00.0: eth2: IOV: VF 2 is enabled mac 42:7F:C3:60:78:60 ixgbe
> :13:00.0: eth2: IOV: VF 3 is enabled mac 46:70:37:00:FC:8C ixgbe
> :13:00.0: eth2: Intel(R) 10 Gigabit Network Connection ixgbe
> :13:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 ixgbe
> :13:00.1: setting latency timer to 64
> ixgbe: I/O Virtualization (IOV) set to 4
> ixgbe: :13:00.1: ixgbe_check_options: FCoE Offload feature 
> disabled
> ADDRCONF(NETDEV_UP): eth2: link is not ready ixgbe :13:00.0: eth2:
> detected SFP+: 5 ixgbe :13:00.1: irq 30 for MSI/MSI-X ixgbe
> :13:00.1: irq 31 for MSI/MSI-X ixgbe :13:00.1: (PCI 
> Express:2.5GT/s:Width x8) 00:1b:21:8e:ae:e5 ixgbe :13:00.1: eth3: MAC:
> 2, PHY: 15, SFP+: 6, PBA No: E68785-003 ixgbe :13:00.1: eth3: 
> Enabled
> Features: RxQ: 1 TxQ: 1 LRO ixgbe :13:00.1: eth3: IOV: VF 0 is 
> enabled mac 8A:75:79:3D:91:45 ixgbe :13:00.1: eth3: IOV: VF 1 is 
> enabled mac
> EA:DB:6E:21:CE:D2 ixgbe :13:00.1: eth3: IOV: VF 2 is enabled mac 
> EE:22:8A:91:7A:AC ixgbe :13:00.1: eth3: IOV: VF 3 is enabled mac
> A2:92:0B:65:4A:24 ixgbe :13:00.1: eth3: Intel(R) 10 Gigabit 
> Network Connection
> ADDRCONF(NETDEV_UP): eth3: link is not ready ixgbe :13:00.0: eth2: 
> NIC Link is Up 10 Gbps, Flow Control: RX/TX
> ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready ixgbe :13:00.1:
> eth3: detected SFP+: 6 ixgbe :13:00.1: eth3: NIC Link is Up 10 
> Gbps, Flow Control: RX/TX
> ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
> 
> 
> 
> --
> 
> 
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft 
> developers is just $99.99! Visual Studio, SharePoint, SQL - plus 
> HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you
subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> ___
> E1000-devel mailing list
> E1000-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit 

Re: [E1000-devel] VFS vs MTU

2012-01-30 Thread Rose, Gregory V
> -Original Message-
> From: Steve O'Brien [mailto:obr...@velocent.com]
> Sent: Monday, January 30, 2012 10:05 AM
> To: e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel] VFS vs MTU
> 
> 
> Has anyone else encountered this problem?
> 
> Sorry, my contact info is:
>   Steve O'Brien
>   obr...@velocent.com
>   Sr. Engineer
>   Velocent Systems

If the Intel 10Gig device you're is based on the 82599 controller then there is 
an errata on that device that prevents use of jumbo frames while in SR-IOV 
mode.  You must disable SR-IOV if you want to use jumbo frames.

The driver will not allow any parameter larger than 1500 for those devices when 
SR-IOV mode is enabled and that is why you are getting the invalid parameter 
error message.

The errata will be fixed in future generations of Intel 10gig controllers.  I 
apologize for the inconvenience.

- Greg

> 
> -Original Message-
> From: Steve O'Brien [mailto:obr...@velocent.com]
> Sent: Thursday, January 26, 2012 1:00 PM
> To: 'e1000-devel@lists.sourceforge.net'
> Subject: VFS vs MTU
> 
> 
> Oh, I hope this isn't a dumb question, but I can't set the MTU to 4096
> using SR-IOV.
> 
> I'm using the X520-SR2 dual 82599 NIC with RedHat 6.0. I use 'modprobe
> ixgbe max_vfs=4,4`, then try to increase the MTU using 'ifconfig eth2 mtu
> 4096', gives me the response `SIOCSIFMTU: Invalid argument`.
> 
> The modprobe appears successful, dmesg is:
> 
> Intel(R) 10 Gigabit PCI Express Network Driver - version 3.7.17-NAPI
> Copyright (c) 1999-2011 Intel Corporation.
> ixgbe :13:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ixgbe
> :13:00.0: setting latency timer to 64
> ixgbe: I/O Virtualization (IOV) set to 4
> ixgbe: :13:00.0: ixgbe_check_options: FCoE Offload feature disabled
> ixgbe :13:00.0: irq 28 for MSI/MSI-X ixgbe :13:00.0: irq 29 for
> MSI/MSI-X ixgbe :13:00.0: (PCI Express:2.5GT/s:Width x8)
> 00:1b:21:8e:ae:e4 ixgbe :13:00.0: eth2: MAC: 2, PHY: 15, SFP+: 5, PBA
> No: E68785-003 ixgbe :13:00.0: eth2: Enabled Features: RxQ: 1 TxQ: 1
> LRO ixgbe :13:00.0: eth2: IOV: VF 0 is enabled mac 36:25:DD:F1:C6:DC
> ixgbe :13:00.0: eth2: IOV: VF 1 is enabled mac 3A:98:30:1A:89:9D ixgbe
> :13:00.0: eth2: IOV: VF 2 is enabled mac 42:7F:C3:60:78:60 ixgbe
> :13:00.0: eth2: IOV: VF 3 is enabled mac 46:70:37:00:FC:8C ixgbe
> :13:00.0: eth2: Intel(R) 10 Gigabit Network Connection ixgbe
> :13:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 ixgbe
> :13:00.1: setting latency timer to 64
> ixgbe: I/O Virtualization (IOV) set to 4
> ixgbe: :13:00.1: ixgbe_check_options: FCoE Offload feature disabled
> ADDRCONF(NETDEV_UP): eth2: link is not ready ixgbe :13:00.0: eth2:
> detected SFP+: 5 ixgbe :13:00.1: irq 30 for MSI/MSI-X ixgbe
> :13:00.1: irq 31 for MSI/MSI-X ixgbe :13:00.1: (PCI
> Express:2.5GT/s:Width x8) 00:1b:21:8e:ae:e5 ixgbe :13:00.1: eth3: MAC:
> 2, PHY: 15, SFP+: 6, PBA No: E68785-003 ixgbe :13:00.1: eth3: Enabled
> Features: RxQ: 1 TxQ: 1 LRO ixgbe :13:00.1: eth3: IOV: VF 0 is enabled
> mac 8A:75:79:3D:91:45 ixgbe :13:00.1: eth3: IOV: VF 1 is enabled mac
> EA:DB:6E:21:CE:D2 ixgbe :13:00.1: eth3: IOV: VF 2 is enabled mac
> EE:22:8A:91:7A:AC ixgbe :13:00.1: eth3: IOV: VF 3 is enabled mac
> A2:92:0B:65:4A:24 ixgbe :13:00.1: eth3: Intel(R) 10 Gigabit Network
> Connection
> ADDRCONF(NETDEV_UP): eth3: link is not ready ixgbe :13:00.0: eth2: NIC
> Link is Up 10 Gbps, Flow Control: RX/TX
> ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready ixgbe :13:00.1:
> eth3: detected SFP+: 6 ixgbe :13:00.1: eth3: NIC Link is Up 10 Gbps,
> Flow Control: RX/TX
> ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
> 
> 
> 
> --
> 
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> ___
> E1000-devel mailing list
> E1000-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTM

Re: [E1000-devel] VFS vs MTU

2012-01-30 Thread Steve O'Brien

Has anyone else encountered this problem?

Sorry, my contact info is:
Steve O'Brien
obr...@velocent.com
Sr. Engineer
Velocent Systems

-Original Message-
From: Steve O'Brien [mailto:obr...@velocent.com] 
Sent: Thursday, January 26, 2012 1:00 PM
To: 'e1000-devel@lists.sourceforge.net'
Subject: VFS vs MTU


Oh, I hope this isn't a dumb question, but I can't set the MTU to 4096 using 
SR-IOV.

I'm using the X520-SR2 dual 82599 NIC with RedHat 6.0. I use 'modprobe ixgbe 
max_vfs=4,4`, then try to increase the MTU using 'ifconfig eth2 mtu 4096', 
gives me the response `SIOCSIFMTU: Invalid argument`.

The modprobe appears successful, dmesg is:

Intel(R) 10 Gigabit PCI Express Network Driver - version 3.7.17-NAPI Copyright 
(c) 1999-2011 Intel Corporation.
ixgbe :13:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ixgbe 
:13:00.0: setting latency timer to 64
ixgbe: I/O Virtualization (IOV) set to 4
ixgbe: :13:00.0: ixgbe_check_options: FCoE Offload feature disabled ixgbe 
:13:00.0: irq 28 for MSI/MSI-X ixgbe :13:00.0: irq 29 for MSI/MSI-X 
ixgbe :13:00.0: (PCI Express:2.5GT/s:Width x8) 00:1b:21:8e:ae:e4 ixgbe 
:13:00.0: eth2: MAC: 2, PHY: 15, SFP+: 5, PBA No: E68785-003 ixgbe 
:13:00.0: eth2: Enabled Features: RxQ: 1 TxQ: 1 LRO ixgbe :13:00.0: 
eth2: IOV: VF 0 is enabled mac 36:25:DD:F1:C6:DC ixgbe :13:00.0: eth2: IOV: 
VF 1 is enabled mac 3A:98:30:1A:89:9D ixgbe :13:00.0: eth2: IOV: VF 2 is 
enabled mac 42:7F:C3:60:78:60 ixgbe :13:00.0: eth2: IOV: VF 3 is enabled 
mac 46:70:37:00:FC:8C ixgbe :13:00.0: eth2: Intel(R) 10 Gigabit Network 
Connection ixgbe :13:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 ixgbe 
:13:00.1: setting latency timer to 64
ixgbe: I/O Virtualization (IOV) set to 4
ixgbe: :13:00.1: ixgbe_check_options: FCoE Offload feature disabled
ADDRCONF(NETDEV_UP): eth2: link is not ready ixgbe :13:00.0: eth2: detected 
SFP+: 5 ixgbe :13:00.1: irq 30 for MSI/MSI-X ixgbe :13:00.1: irq 31 for 
MSI/MSI-X ixgbe :13:00.1: (PCI Express:2.5GT/s:Width x8) 00:1b:21:8e:ae:e5 
ixgbe :13:00.1: eth3: MAC: 2, PHY: 15, SFP+: 6, PBA No: E68785-003 ixgbe 
:13:00.1: eth3: Enabled Features: RxQ: 1 TxQ: 1 LRO ixgbe :13:00.1: 
eth3: IOV: VF 0 is enabled mac 8A:75:79:3D:91:45 ixgbe :13:00.1: eth3: IOV: 
VF 1 is enabled mac EA:DB:6E:21:CE:D2 ixgbe :13:00.1: eth3: IOV: VF 2 is 
enabled mac EE:22:8A:91:7A:AC ixgbe :13:00.1: eth3: IOV: VF 3 is enabled 
mac A2:92:0B:65:4A:24 ixgbe :13:00.1: eth3: Intel(R) 10 Gigabit Network 
Connection
ADDRCONF(NETDEV_UP): eth3: link is not ready ixgbe :13:00.0: eth2: NIC Link 
is Up 10 Gbps, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready ixgbe :13:00.1: eth3: 
detected SFP+: 6 ixgbe :13:00.1: eth3: NIC Link is Up 10 Gbps, Flow 
Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready



--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired