From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: ruzicka.jakub@gmail.com, netdev@vger.kernel.org
Subject: Re: via-rhine interrupts
Date: Thu, 19 Aug 2010 19:09:12 +0200 [thread overview]
Message-ID: <20100819170912.GA2387@del.dom.local> (raw)
In-Reply-To: <20100818.234939.71574087.davem@davemloft.net>
On Wed, Aug 18, 2010 at 11:49:39PM -0700, David Miller wrote:
> From: Jarek Poplawski <jarkao2@gmail.com>
> Date: Sun, 15 Aug 2010 22:04:31 +0200
>
> > I've just tested it using a simplistic patch below, which skips
> > some napi receiving by doing it only every second jiffie (on even
> > ones), and I've got around 30% less interrupts from via-rhine,
> > which seems to suggest napi works OK, but there is too low
> > traffic (or too fast soft interrupt handling) to affect hard
> > interrupts. (Btw, probably CONFIG_HZ can matter here a bit too.
> > I tested with 1000.)
>
> 100Mbit on any modern system isn't going to trigger NAPI much at all
> even with near full link utilization.
>
> The simply cpu processes the packets too fast for them to gather up
> much at all.
>
> Some improvement in polling could be gained if the via-rhine has some
> HW interrupt mitigation settings. However after a quick perusal of
> the driver I don't see anything about this. The mitigation ethtool
> ops aren't implemented either, so I'm not optimistic :-)
>
Yes, now I see the old comments (pre 2.6.27) mentioned 10kpps
threshold, which wasn't reached in Jakub's example.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=32b0f53e5bc80b87fd20d4d78a0e0cb602c9157a
Jarek P.
prev parent reply other threads:[~2010-08-19 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 11:03 via-rhine interrupts Jakub Ružička
2010-08-15 20:04 ` Jarek Poplawski
2010-08-19 6:49 ` David Miller
2010-08-19 17:09 ` Jarek Poplawski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100819170912.GA2387@del.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ruzicka.jakub@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).