From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: netdev@vger.kernel.org
Subject: Network driver "test suite"
Date: Wed, 12 Apr 2017 10:16:17 +1000 [thread overview]
Message-ID: <1491956177.7236.34.camel@kernel.crashing.org> (raw)
Hi folks !
Does anybody knows of an existing kind of automated "test suite" for a
network/ethernet driver ?
IE. Something we could run both on the "tested" driver and a cross-over
"known good" peer (possibly the latter set to promisc & no offload for
proper analysis), that would out the driver through a whole bunch of
tests, such as verifying the checksum offload on a various combinations
of headers lenghts and encapsulation, vlan stuff, multicast filters,
etc... ?
I've hacking on a driver recently and ended up "manually" testing a
bunch of these things using a palette of tools (iperf, nuttcp, some
multicast hack I have around, etc... along with tcpdump) but it feels
like this is the kind of things that could be greatly automated.
Cheers,
Ben.
next reply other threads:[~2017-04-12 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 0:16 Benjamin Herrenschmidt [this message]
2017-04-12 0:36 ` Network driver "test suite" Florian Fainelli
2017-04-12 7:47 ` Benjamin Herrenschmidt
2017-04-12 7:18 ` Corentin Labbe
[not found] <20050105152635.290ad9c0@dxpl.pdx.osdl.net>
2005-01-12 1:32 ` Fw: Network driver test suite? Craig Thomas
2005-01-12 16:24 ` David Hollis
2005-01-12 17:14 ` Craig Thomas
2005-01-12 18:10 ` Stephen Hemminger
2005-01-12 18:21 ` Randy.Dunlap
2005-01-13 15:29 ` Cliff White
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 20:19 David Hollis
2005-01-05 22:10 ` Jeff Garzik
2005-01-06 13:43 ` David Hollis
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=1491956177.7236.34.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--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).