Felix,
Actually i based my comments on the profiles you posted ;->
Are you running any other nics? If not that profile does look strange.
cheers,
jamal
On Sun, 2003-08-10 at 03:32, Felix Radensky wrote:
> Hi, Jamal
>
> I guess you were not reading my first posting
> very carefully :)
>
> 2.4.22 has NAPI capable e1000 driver and I've
> compiled the driver with NAPI support.
>
> So running non-NAPI driver is not my problem.
>
> Felix.
>
> jamal wrote:
> > Actually seems his biggest problem is he is not running
> > the NAPI driver
> >
> > cheers,
> > jamal
> >
> > On Thu, 2003-08-07 at 15:09, Robert Olsson wrote:
> >
> > > Felix Radensky writes:
> > > > Thanks for your help, Ben. What is skb-recycle patch
> > > > and where can I find it ?
> > >
> > > It's experimental and not updated for almost a year and current
> > > implementation does not add anything to SMP. Got some idea how
> > > to improve this... but try to keep to slab as long as possible
> > > it has been improved.
> > >
> > > Routing/bridging on SMP has affinty problem. If you are passing
> > > skb's say from eth0 to eth1 and they are bound on different CPU's
> > > you get cache boucing since the TX-interrupts come on another CPU.
> > >
> > > In a recent test with pktgen:
> > > 300 kpps with TX interrupts on same CPU as sender.
> > > 198 kpps with TX intr on different CPU as sender.
> > >
> > > Recycling tries to address this but current implementation fails
> > > as said.
> > >
> > > But you are probably hit by something else... Check were the drops
> > > happens qdisc?. NIC ring RX/TX size, Number of interrupts. ksoftird
> > > priority, link HW_FLOW control, checksumming, affinity etc.
> > >
> > >
> > > Cheers.
> > > --ro
> > >
> > >
> > >
> >
> >
>
|