Re: Dropping Packets in 2.6.17

Danial Thom
2006-06-22T17:10:47Z

--- Pádraig Brady <P@draigBrady.com> wrote:

> Danial Thom wrote:
> >
> > --- Pádraig Brady <P@draigBrady.com> wrote:
> >
> >>For reference with 2.4.20 on a dual 3.4GHz
> xeon
> >>and 2 x e1000 cards, I was able to capture,
> >>classify and do statistical calculations
> >>on 625Kpps per interface (1.3 million pps).
> >
> > Unfortunately I can do that much with FreeBSD
> 4.x
> > with 1 2.0Ghz opteron, so its not a very
> > compelling case to have to spend twice as
> much on
> > hardware to use LINUX. However 2.4 seemed
> much
> > better than 2.6 in this regard. 2.6 wants to
> drop
> > a lot more packets. The goal of using 2.6 is
> to
> > utilize DP better, but it obviously has to
> > perform better than a UP Freebsd box.
>
> NC.
>
> > What ITR setting are using for the e1000
> driver?
>
> I didn't use ITR, I used NAPI.
>

If thats the case then your "system" would have
the same problem that I'm encountering, since
polling results in buckets of packets being
dropped with heavy userland activity.

Since you can control exactly how many interrupts
are generated and how often, there should be no
advantage to polling, unless LINUX interrupt
processing is badly broken, which seems like a
strong possibility.

This should work quite naturally without having
to use kludges like polling, enormous receive
rings or memory cheating.

DT

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around