Skip to contentSkip to conversation

Network driver "test suite"

DISCUSSION Benjamin Herrenschmidt 3 participants 4 messages Apr 12, 2017

Subsystems (2)
lore
Share & tools
lore
#0 lore 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.

#1 lore raw

Hi,

Quoted 11 lines · Benjamin Herrenschmidt

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... ?

You could start with using LNST:

https://github.com/jpirko/lnst

and there is also Ostinato which is a great way to get access to something IXIA-like, but all configurable in software through python bindings. Andrew's dsa-tests make use of it, but they would not be directly portable here [1].

[1]: https://github.com/lunn/dsa-tests

Signature · 1 line
Florian
#2 lore raw
Quoted 11 lines · Florian Fainelli

You could start with using LNST:

https://github.com/jpirko/lnst

and there is also Ostinato which is a great way to get access to something IXIA-like, but all configurable in software through python bindings. Andrew's dsa-tests make use of it, but they would not be directly portable here [1].

[1]: https://github.com/lunn/dsa-tests

Thanks. I'll play with these when I have a bit of spare time !

Cheers,
Ben.

#3 lore raw
In reply to Benjamin Herrenschmidt
Quoted 12 lines · Benjamin Herrenschmidt

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... ?

Quoted 8 lines

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.

I have started to add some tests to kselftests (tools/testing/selftests/net/netdevice.sh)
The major intent is that thoses tests could be run without any user directive. (and so could be usefull in kernelci) I just need to share the next serie of patch.

Regards