* Re: Packet Overrun for traffic over 1 Gbps
[not found] ` <e31d15d70906200254m3ab04065y3f4b853d0de72471@mail.gmail.com>
@ 2009-06-20 12:11 ` Eric Dumazet
0 siblings, 0 replies; only message in thread
From: Eric Dumazet @ 2009-06-20 12:11 UTC (permalink / raw)
To: Deepak Vishwakarma; +Cc: linux-kernel, Linux Netdev List
Deepak Vishwakarma a écrit :
> Hi,
>
> I have a high end server machine(multi core and large memory space)
> with 10 Gbps NIC. With linux kernel 2.6.18 it is giving packet overrun
> as traffic goes beyond 1.5 Gbps. I need suggestions in tuning kernel
> so that it can handle higher traffic rates.
>
> I have a 10 Gbps test bed to test the capability of server, equipped
> with 10Gig switch and traffic is generated from many 1Gig machines. I
> have tested server machine by gradually increasing the incoming
> traffic rate and it's starting to do packet overrun as it crosses 1
> Gbps.
>
> The 10 Gig NIC is from broadcom, (netxtreme). I have tested NIC with
> the driver shipped by vendor that is bnx2x v 1.44 and latest available
> on net, both are giving more or less same result. Will it help to try
> latest kernel 2.6.30 ? or what could be other possible tuning in
> kernel to make it handle high traffic (3-4 Gbps).
>
This is quite difficult to generically answer to your question without
more data from you about the workload, and your setup.
(kind of traffic, is it UDP, (unicast or multicast), TCP, number
of flows...)
One can easily stress a high end server with a moderate network
traffic, depending on the work done by receiver. I have some
workloads that saturate the cpu handling RX queue, even way before
1 Gbps level, because this cpu has to wakeup tasks at high rate.
With small application changes, it is also possible to reduce
number of wakeups done by the receiver cpu, giving more cpu
cycles to network stack.
One possible way to get high traffic, even with fast cpus/cores,
is to use a NIC that is able to split the load into multiple RX/TX queues,
so that several cpus can work together and process data concurrently.
One important thing is to make sure NIC interrupts for a given
RX queue are serviced by only one CPU, to avoid cache line ping
pongs between cpus. You can double the traffic with
proper irq affinities.
Many scalability improvements were done in network stack between
2.6.18 and 2.6.30, so you should try a recent kernel.
Multi queue management definitly improved a lot during last releases.
^ permalink raw reply [flat|nested] only message in thread