Modifying the Two-Card Network Card Miniport Driver Test

Article
06/30/2006

The Two-Card Network Card Miniport Driver Test executes the tux –o –d ndt_2c command line on default execution. You can modify the test by editing the command line. For information about how to edit the command line for a test, see Editing the Command Line for a Test. The following table shows the modifications you can make to the test.

To modify the Two-Card Network Card Miniport Driver Test

To	Add this command-line parameter
Log information when a test confirms that a packet has been sent or received.	`-packets`
Disable unbinding of other protocol drivers from the test adapter before the test is run.	`-nounbind`
Print debug output at intervals specified by the value of delay. The debug output contains information about the state of packet buffers for the test. The value of delay is given in units of milliseconds (ms).	`-beat <delay>`
Skip test cases 5 and 6.	`-nostress`
Set the interval, in milliseconds (ms), between packets sent during test cases 5 and 6. The default interval is 10 ms.	`-delay <interval>`

For information about configuring the target device and development workstation for the test, see Running the Two-Card Network Card Miniport Driver Test.

The following table shows the various test cases for the Two-Card Network Card Miniport Driver Test.

Test case	Description
1: Send packets	Sends packets using the NdisSendPackets function. The test uses various burst and packet sizes and logs a failure if any problems occur during NdisSendPackets. This test case uses either a minimum packet size of 64/96 bytes, the maximum packet size supported by the medium, or an average of these two sizes.
2: Receive packets	Tests whether the card is able to correctly receive packets on its hardware Media Access Control (MAC) address.
3: Filter receive	Tests whether the card is able to correctly receive packets with various addressing types. The test uses one open instance to send and eight instances to receive. Each of the eight receiving instances has a different filter setting, which allows all supported filter settings to be tested quickly and verifies that an open instance does not receive a packet that it should not receive.
4: Multicast receive	Tests whether the card is able to receive on as many different multicast addresses as the card claims to support. The test uses all available multicast addresses and attempts to send packets to each of those addresses. The test also verifies that packets are only received on the multicast addresses that are active.
5: Stress send	Executes a stress test between the test card and the support card on the target device. The test card sends packets and the support card receives packets. The test runs for 10 iterations with various buffering options. The test also verifies that the test card can send packets of differing size at a faster rate and can simultaneously receive different types of acknowledgement packets. Packet loss may occur in this test.
6: Stress receive	Executes a stress test between the test card and the support card on the target device. The support card sends packets and the test card receives packets. The test runs for five iterations with various buffering options. The test also verifies that the test card can receive packets of differing size at a faster rate and can simultaneously send different types of acknowledgement packets. Packet loss is common during this test. The main criterion for success is that the miniport driver should be able to handle send and receive requests with various buffer configurations.

Remarks

This test library can have one or more optional command-line entries to change the behavior of the test. To specify one or more optional command-line entries to the test library, you must use the –c command-line option. This option forces Tux to pass the specified string into the test library.

Share via

Modifying the Two-Card Network Card Miniport Driver Test

Remarks

See Also

Additional resources