[Top] [All Lists]

Re: NAPI, e100, and system performance problem

To: Greg Banks <gnb@xxxxxxx>
Subject: Re: NAPI, e100, and system performance problem
From: jamal <hadi@xxxxxxxxxx>
Date: Wed, 20 Apr 2005 11:15:31 -0400
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, akepner@xxxxxxx, jesse.brandeburg@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <>
Organization: unknown
References: <C925F8B43D79CC49ACD0601FB68FF50C03A633C7@orsmsx408> <> <1113855967.7436.39.camel@localhost.localdomain> <> <> <>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Thu, 2005-21-04 at 00:56 +1000, Greg Banks wrote:

> We have a stats package called PCP (see which samples
> all kinds of stuff out of /proc at a configurable polling frequency,
> default 2 sec, and provides scrolling graphs.  We've also done some
> profiling work using the SGI kernprof patch in 2.4 kernels and
> oprofile in 2.6 kernels.

this may not be sufficient to debug; that PCP sounds like a hog in its
own merit polling /proc.

Actually, lets start by saying this:
If you problem is PIO being too expensive on your machines, then the
solution maybe for you to set coalescing parameters appropriately. This
is a known issue - "fixing NAPI" requires complicating things for the
majority who dont have the same problem as you.
The issue pointed out by Rick Jones that you sacrifice latency is still
valid. Additionaly, with many NICs in place, coalescing is not gonna cut

Having said that - here are some items that will be useful to collect
before and after a run:

- netstat -s output
- /proc/net/softnet_stat
- ifconfig output
- tc -s qdisc on the interfaces 
- oprofile 
- any other thing you could come up with like some of the stuff you
posted recently on how many packets/interupt are processed with and
without NAPI.
- preferably run UDP tests so we dont have to think hard about stats
like retransmits etc.
- And as pointed by Dave, pick the latest kernel.


<Prev in Thread] Current Thread [Next in Thread>