[Top] [All Lists]

Re: _High_ CPU usage while routing (mostly) small UDP packets

To: Karsten Desler <kdesler@xxxxxxxxxx>
Subject: Re: _High_ CPU usage while routing (mostly) small UDP packets
From: jamal <hadi@xxxxxxxxxx>
Date: 08 Dec 2004 08:27:18 -0500
Cc: Willy Tarreau <willy@xxxxxxxxx>, P@xxxxxxxxxxxxxx, "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20041208130845.GA5036@xxxxxxxxxx>
Organization: jamalopolous
References: <20041206205305.GA11970@xxxxxxxxxx> <20041206134849.498bfc93.davem@xxxxxxxxxxxxx> <20041206224107.GA8529@xxxxxxxxxx> <41B58A58.8010007@xxxxxxxxxxxxxx> <20041207112139.GA3610@xxxxxxxxxx> <20041208053953.GC17946@xxxxxxxxxxxxxxxx> <20041208130845.GA5036@xxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 2004-12-08 at 08:08, Karsten Desler wrote:

> I was running mit ITR=3000, but as a test to see if NAPI works, I
> disabled ITR on eth0 bringing the int/s rate up to 50k.
> Is that normal? I always though NAPI was supposed to kick in way earlier.
> Anyways, I'm going to try different ITR settings to see if they make any
> difference.

The one time you would need this ITR crap is when you are running low
traffic (relatively speaking: which could mean anything below 100Kpps
depending on h/ware). NAPI will consume a little more CPU
otherwise - given it does an extra IO (if it kicks in and out on every
packet or two). Granted you are doing some new types of tests, so
you may be seeing some things we havent experienced before.

Can you put a printk in ->open() of e1000 with
#if napi is defined
printk("%s: NAPI is on\n",dev->name);

This should print on ifconfig up and indicate whether NAPI is on or not.


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