netdev
[Top] [All Lists]

Re: RFC: NAPI packet weighting patch

To: greearb@xxxxxxxxxxxxxxx
Subject: Re: RFC: NAPI packet weighting patch
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Fri, 03 Jun 2005 11:49:50 -0700 (PDT)
Cc: john.ronciak@xxxxxxxxx, Robert.Olsson@xxxxxxxxxxx, jdmason@xxxxxxxxxx, shemminger@xxxxxxxx, hadi@xxxxxxxxxx, mitch.a.williams@xxxxxxxxx, netdev@xxxxxxxxxxx, ganesh.venkatesan@xxxxxxxxx, jesse.brandeburg@xxxxxxxxx
In-reply-to: <42A0A25C.8000503@candelatech.com>
References: <468F3FDA28AA87429AD807992E22D07E0450BFE8@orsmsx408> <42A0A25C.8000503@candelatech.com>
Sender: netdev-bounce@xxxxxxxxxxx
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Fri, 03 Jun 2005 11:33:00 -0700

> Is this implying that having the NAPI poll do less work per poll
> of the driver actually increases performance?  I would have guessed that
> the opposite would be true.

Exactly my thoughts as well :)

> Maybe the poll is disabling the IRQs on the NIC for too long, or something
> like that?

In a reply I just sent out to this thread, I postulate that the
jiffies check is hitting earlier with a lower weight value, a quick
look at /proc/net/softnet_stat during their testing will confirm or
deny this theory.

It could also just be a simple bug in the dev->quota accounting
somewhere.

Note that, in all of this, I do not have any objections to providing
a way to configure the dev->weight values.  I will be applying Stephen
Hemminger's patches.

But I think we MUST find out the reason for the observed behavior,
especially in the single-adapter case since the result is so illogical.
We could find an important bug in the NAPI implementation, or learn
something new about how NAPI behaves.

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