From: Mark Smith <lk-netdev@lk-netdev•nosense.org>
To: netdev@vger•kernel.org
Cc: greearb@candelatech•com
Subject: Ethernet low-level frame debugging support
Date: Sun, 19 Jun 2011 10:44:31 +0930 [thread overview]
Message-ID: <20110619104431.23a22fe9@opy.nosense.org> (raw)
Hi,
Firstly, I think this is a potentially quite useful feature for
networking people and that I hope it makes it into the kernel proper.
One thing I've thought is that perhaps it might be made and named a bit
more generally, as NICs will also drop frames for other reasons other
than FCs failures e.g. runt frames. So perhaps something like "true
promiscuous" or "full promiscuous" might be a more general name, and if
it is enabled, then all NIC error checking that can be switched off is
switched off. Looking at the chipset data sheets for a few NICs that I
have / have had (netgear FA312 (natsemi ns83815), smc epic100, ne2000),
they all seem to have registers which allow switching off many if not
all of the NIC error checking settings.
The other thing I've thought could be useful would be to be able to
send runts by not padding the frames when they're less then 64 bytes.
I've been able to test if this is possible with the netgear FA312, as
the chipset does the padding. I connected it back to back with an
e1000e I have, switched off the chipset automatic padding on the FA312,
sent small traffic, and then saw that the e1000e's internal
rx_short_length_errors counter correspondingly increased. Of course I
can't see them with tcpdump on the e1000e because it is dropping them.
Regards,
Mark.
next reply other threads:[~2011-06-19 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 1:14 Mark Smith [this message]
2011-06-19 20:19 ` Ethernet low-level frame debugging support Ben Greear
2011-06-19 23:27 ` Mark Smith
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=20110619104431.23a22fe9@opy.nosense.org \
--to=lk-netdev@lk-netdev$(echo .)nosense.org \
--cc=greearb@candelatech$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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