Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/Networking Drivers/Problem: Intel 82567LM doesn't work with jumbo frames/List of Posts
Forum Topic - Problem: Intel 82567LM doesn't work with jumbo frames: (18 Items)
   
Update
Sven Fieske
03/01/2010 4:42 AM
post48485
Problem: Intel 82567LM doesn't work with jumbo frames   
Hello.

I like to use a on board Intel 82567LM NIC with jumbo frames under QNX 6.4.1, but it doesn't work.
The nicinfo returned many squelch test errors on this interface.
Intel says this NIC supports 9k jumbo frames.

Device-ID of the NIC is 10de and it starts with the e1000.so driver.
I have configured the NIC as follows:

ifconfig wm0 ip4csum tcp4csum udp4csum
ifconfig wm0 mtu 8100
ifconfig wm0 192.168.101.100/24 up

It works if I choice a mtu of 1500 but not with 8100.

What can be the problem?

best regards,

Sven Fieske
Andrew Boyd(deleted)
03/01/2010 9:50 AM
post48509
RE: Problem: Intel 82567LM doesn't work with jumbo frames   
> The nicinfo returned many squelch test errors on this interface.

My bad.  I hi-jacked that counter for rx fifo overruns.

Regardless, you are seeing excessive bus latency which 
is causing you to lose rxd packets.  If possible, you
should get rid of those.

> Intel says this NIC supports 9k jumbo frames.

Sure does.  However jumbo frames are not part of
the IEEE (or any other) standard, so support for it 
is spotty.

Because I like jumbo frames (eg for high throughput and
benchmarks) the now-deprecated devnp-i82544.so had support
for jumbo frames.  However, I am not sure if the new
devnp-e1000.so supports them or not, which is reasonable,
because like I said, jumbo frames are not part of any 
standard and hence is not required.  Heck, people don't
even agree what a jumbo frame is.

Hugh?

--
aboyd
Hugh Brown
03/01/2010 10:04 AM
post48511
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
The driver should support jumbo frames, but it hasn't been tested.


On 10-03-01 9:50 AM, "Andrew Boyd" <community-noreply@qnx.com> wrote:

> 
>> The nicinfo returned many squelch test errors on this interface.
> 
> My bad.  I hi-jacked that counter for rx fifo overruns.
> 
> Regardless, you are seeing excessive bus latency which
> is causing you to lose rxd packets.  If possible, you
> should get rid of those.
> 
>> Intel says this NIC supports 9k jumbo frames.
> 
> Sure does.  However jumbo frames are not part of
> the IEEE (or any other) standard, so support for it
> is spotty.
> 
> Because I like jumbo frames (eg for high throughput and
> benchmarks) the now-deprecated devnp-i82544.so had support
> for jumbo frames.  However, I am not sure if the new
> devnp-e1000.so supports them or not, which is reasonable,
> because like I said, jumbo frames are not part of any
> standard and hence is not required.  Heck, people don't
> even agree what a jumbo frame is.
> 
> Hugh?
> 
> --
> aboyd
> 
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post48509
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
Sven Fieske
03/01/2010 10:14 AM
post48513
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
If i run my jumbo frame app with a Intel 82574L NIC (10d3), it works very fine.

What can I do now?
I must use jumbo frames!
Andrew Boyd(deleted)
03/01/2010 10:19 AM
post48514
RE: Problem: Intel 82567LM doesn't work with jumbo frames   
> I must use jumbo frames!

Two options come to mind:

1) download the source and fix it.  It's probably not
a big change, if devnp-e1000.so supports jumbo frames
for other DID's.

2) create a PR and assign it to Bert for prioritization.

--
aboyd
Sönke Nielsen
03/03/2010 3:43 AM
post48683
Re: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
Raised PR# 75065.
Mario Charest
03/01/2010 11:19 AM
post48526
RE: Problem: Intel 82567LM doesn't work with jumbo frames   

> -----Original Message-----
> From: Hugh Brown [mailto:community-noreply@qnx.com]
> Sent: Monday, March 01, 2010 10:05 AM
> To: drivers-networking
> Subject: Re: Problem: Intel 82567LM doesn't work with jumbo frames
> 
> The driver should support jumbo frames, but it hasn't been tested.
> 

Works for us.

> 
> On 10-03-01 9:50 AM, "Andrew Boyd" <community-noreply@qnx.com> wrote:
> 
> >
> >> The nicinfo returned many squelch test errors on this interface.
> >
> > My bad.  I hi-jacked that counter for rx fifo overruns.
> >
> > Regardless, you are seeing excessive bus latency which
> > is causing you to lose rxd packets.  If possible, you
> > should get rid of those.
> >
> >> Intel says this NIC supports 9k jumbo frames.
> >
> > Sure does.  However jumbo frames are not part of
> > the IEEE (or any other) standard, so support for it
> > is spotty.
> >
> > Because I like jumbo frames (eg for high throughput and
> > benchmarks) the now-deprecated devnp-i82544.so had support
> > for jumbo frames.  However, I am not sure if the new
> > devnp-e1000.so supports them or not, which is reasonable,
> > because like I said, jumbo frames are not part of any
> > standard and hence is not required.  Heck, people don't
> > even agree what a jumbo frame is.
> >
> > Hugh?
> >
> > --
> > aboyd
> >
> >
> >
> >
> > _______________________________________________
> >
> > Networking Drivers
> > http://community.qnx.com/sf/go/post48509
> >
> 
> --
> Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
> QNX Software Systems Ltd.        (613) 591-3579           (fax)
> 175 Terence Matthews Cres.       email:  hsbrown@qnx.com
> Kanata, Ontario, Canada.
> K2M 1W8
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post48511
>
Philipp Lutz
04/27/2010 10:39 AM
post52896
Re: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
yes, it works but look at the latency. at the moment i'm doing network performance measurements and i get worst case 
latencies between 1-5 seconds if you send UDP packets which are around 60kbytes in size.
a smaller MTU works way better in terms of reliability, here you get constant and reasonable latencies.

i think the stack or driver has massive problems with frames greater than the standard size of 1500 bytes, while the 
packet-size itself is not the problem.
Philipp Lutz
04/28/2010 4:08 AM
post52967
Re: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
I just tested the devnp-e1000.so driver instead of the devnp-i82544.so and got way better results with jumboframes (9000
 bytes).
it seems that this is a device driver related problem.
my latencies drastically decrease when i want to transmit UDP packets of the size of 64000 bytes when i use a MTU of 
9000.

unlike the devnp-i82544.so device driver the devnp-e1000.so seems to handle jumboframes very well. 
btw.: I'm using a 82572EI chipset
Mario Charest
04/28/2010 8:14 AM
post52977
RE: RE: Problem: Intel 82567LM doesn't work with jumbo frames   

> -----Original Message-----
> From: Philipp Lutz [mailto:community-noreply@qnx.com]
> Sent: Wednesday, April 28, 2010 4:09 AM
> To: drivers-networking
> Subject: Re: RE: Problem: Intel 82567LM doesn't work with jumbo frames
> 
> I just tested the devnp-e1000.so driver instead of the devnp-i82544.so
> and got way better results with jumboframes (9000 bytes).
> it seems that this is a device driver related problem.
> my latencies drastically decrease when i want to transmit UDP packets
> of the size of 64000 bytes when i use a MTU of 9000.

Hum?  A UDP packet of 64000?  I though UDP packet always had to be smaller than the MTU?

> 
> unlike the devnp-i82544.so device driver the devnp-e1000.so seems to
> handle jumboframes very well.
> btw.: I'm using a 82572EI chipset
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post52967
>
Patrik Lahti
04/28/2010 9:18 AM
post52991
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
> I though UDP packet always had to be smaller than the MTU?
>    

The UDP datagram size is limited by: the 16bit UDP length field in the 
UDP header and the maximum size of an IP datagram and any implementation 
limits, less the size of the IP header and any options (IPv4 case) or 
extension headers (IPv6 case).

If the (P)MTU is smaller, then the packet will simply be fragmented at 
the IP layer.

/P
Mario Charest
04/28/2010 10:01 AM
post53003
RE: Problem: Intel 82567LM doesn't work with jumbo frames   

> -----Original Message-----
> From: Patrik Lahti [mailto:community-noreply@qnx.com]
> Sent: Wednesday, April 28, 2010 9:18 AM
> To: drivers-networking
> Subject: Re: Problem: Intel 82567LM doesn't work with jumbo frames
> 
> 
> > I though UDP packet always had to be smaller than the MTU?
> >
> 
> The UDP datagram size is limited by: the 16bit UDP length field in the
> UDP header and the maximum size of an IP datagram and any
> implementation
> limits, less the size of the IP header and any options (IPv4 case) or
> extension headers (IPv6 case).
> 
> If the (P)MTU is smaller, then the packet will simply be fragmented at
> the IP layer.

What happen on the receiving end?

> 
> /P
> 
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post52991
>
Patrik Lahti
04/28/2010 10:18 AM
post53006
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
>>> I though UDP packet always had to be smaller than the MTU?
>>>
>>>        
>> The UDP datagram size is limited by: the 16bit UDP length field in the
>> UDP header and the maximum size of an IP datagram and any
>> implementation
>> limits, less the size of the IP header and any options (IPv4 case) or
>> extension headers (IPv6 case).
>>
>> If the (P)MTU is smaller, then the packet will simply be fragmented at
>> the IP layer.
>>      
> What happen on the receiving end?
>    

Not sure if this is what you're asking, but they get reassembled at the 
IP layer and passed up UDP and queued on the socket (if there is one)...
/P
Hugh Brown
04/28/2010 8:32 AM
post52981
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
Good news! Thanks for the update.


On 10-04-28 4:08 AM, "Philipp Lutz" <community-noreply@qnx.com> wrote:

> I just tested the devnp-e1000.so driver instead of the devnp-i82544.so and got
> way better results with jumboframes (9000 bytes).
> it seems that this is a device driver related problem.
> my latencies drastically decrease when i want to transmit UDP packets of the
> size of 64000 bytes when i use a MTU of 9000.
> 
> unlike the devnp-i82544.so device driver the devnp-e1000.so seems to handle
> jumboframes very well.
> btw.: I'm using a 82572EI chipset
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post52967
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
Philipp Lutz
04/30/2010 6:16 AM
post53276
Re: Problem: Intel 82567LM doesn't work with jumbo frames   
I tested again. my setup was slightly different compared to the last time. for the latency measurements this time I used
 a dedicated network interface with a point-to-point connection and separate stacks.
now the devnp-i82544.so shows consistent and reasonable performance even when jumbo-frames have been used, though the 
devnp-e1000.so provided far better performance in every respect.

here are some provided requirements for my tests:
- normal network stack uses default priorities
- network stack used for performance measurments: 200, device driver prio: 220
- test application prio: 60
- 100us delay between UDP send invocations
- set system tick length to 10us
- timestamps via ClockCycles() calls
Andrew Boyd(deleted)
04/28/2010 9:42 AM
post52998
RE: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
> the devnp-e1000.so driver instead of the devnp-i82544.so

Please keep in mind that we are phasing out the original
devnp-i82544.so driver because it is incredibly difficult
to keep up with the plethora of slightly-different nics
from intel with a home-brewed solution.

Over time, this gap will become more noticeable, esp with
newer nics.

--
aboyd
Philipp Lutz
04/30/2010 2:40 AM
post53268
Re: RE: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
> Please keep in mind that we are phasing out the original
> devnp-i82544.so driver because it is incredibly difficult
> to keep up with the plethora of slightly-different nics
> from intel with a home-brewed solution.
> 
> Over time, this gap will become more noticeable, esp with
> newer nics.

does this mean that you are going to neglect the broad support of intel nics or rather support only one general device 
driver for intel nics (devnp-e1000.so)?
Andrew Boyd(deleted)
04/30/2010 7:34 AM
post53279
RE: RE: RE: Problem: Intel 82567LM doesn't work with jumbo frames   
 
> does this mean that you are going to neglect the broad support of intel nics 
 
No, no, no.
 
> or rather support only one general device driver for intel nics (devnp-e1000.so)?
 
Yes, yes, yes.
 
--
aboyd

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems