From: linux@horizon.com
To: netdev@vger.kernel.org
Cc: linux@horizon.com
Subject: arp-scan triggers via-velocity "eth0: excessive work at interrupt"
Date: 12 Jun 2007 21:56:38 -0400 [thread overview]
Message-ID: <20070613015638.31637.qmail@science.horizon.com> (raw)
It kind of surprised me that sending 254 arp packets by using the arp-scan
tool (http://www.nta-monitor.com/tools/arp-scan/) on a /24 consistently
triggers a burst of "eth0: excessive work at interrupt."
This is a 600 MHz PIII, 2.6.22-rc4, via-velocity driver.
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 601.406
cache size : 512 KB
00:09.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter [1106:3119] (rev 11)
Just double-checking... the program actually sent 463 packets (256 +
a retry to all those that didn't respond to the first one), and triggers
11 copies of the kernel message.
Command line: arp-scan -I eth0 -l [-v]
next reply other threads:[~2007-06-13 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 1:56 linux [this message]
2007-06-13 18:39 ` arp-scan triggers via-velocity "eth0: excessive work at interrupt" Stephen Hemminger
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=20070613015638.31637.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=netdev@vger.kernel.org \
/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).