Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Mohan Prasad J <mohan.prasad@microchip.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<kuba@kernel.org>, <andrew@lunn.ch>
Cc: <edumazet@google.com>, <pabeni@redhat.com>, <shuah@kernel.org>,
	<mohan.prasad@microchip.com>, <linux-kernel@vger.kernel.org>,
	<linux-kselftest@vger.kernel.org>, <horms@kernel.org>,
	<brett.creeley@amd.com>, <rosenp@gmail.com>,
	<UNGLinuxDriver@microchip.com>, <willemb@google.com>
Subject: [PATCH net-next v2 0/3] nic_basic_tests: Add selftest for doing basic tests of NIC driver
Date: Tue, 17 Sep 2024 08:04:06 +0530	[thread overview]
Message-ID: <20240917023525.2571082-1-mohan.prasad@microchip.com> (raw)

The series of patches are for doing basic tests of NIC driver.
Test comprises checks for auto-negotiation, speed,
duplex state and throughput between local NIC and partner.
Tools such as ethtool, iperf3 are used.

Signed-off-by: Mohan Prasad J <mohan.prasad@microchip.com>
---
Changes in v2:
- Changed the hardcoded implementation of speed, duplex states,
  throughput to generic values, in order to support all type
  of NIC drivers.
- Test executes based on the supported link modes between local
  NIC driver and partner.
- Instead of lan743x directory, selftest file is now placed in
  /selftests/drivers/net/hw.
---
Mohan Prasad J (3):
  selftests: nic_basic_tests: Add selftest file for basic tests of NIC
  selftests: nic_basic_tests: Add selftest case for speed and duplex
    state checks
  selftests: nic_basic_tests: Add selftest case for throughput check

 .../testing/selftests/drivers/net/hw/Makefile |   1 +
 .../drivers/net/hw/nic_basic_tests.py         | 230 ++++++++++++++++++
 2 files changed, 231 insertions(+)
 create mode 100644 tools/testing/selftests/drivers/net/hw/nic_basic_tests.py

-- 
2.43.0


             reply	other threads:[~2024-09-17  9:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  2:34 Mohan Prasad J [this message]
2024-09-17  2:34 ` [PATCH net-next v2 1/3] selftests: nic_basic_tests: Add selftest file for basic tests of NIC Mohan Prasad J
2024-09-17 15:35   ` Andrew Lunn
2024-09-18 10:30     ` Mohan.Prasad
2024-09-18 12:05       ` Andrew Lunn
2024-09-19 10:44         ` Mohan.Prasad
2024-09-19 14:51           ` Andrew Lunn
2024-09-17 15:48   ` Andrew Lunn
2024-09-18 10:32     ` Mohan.Prasad
2024-09-18 12:11       ` Andrew Lunn
2024-09-17 15:56   ` Andrew Lunn
2024-09-18 10:35     ` Mohan.Prasad
2024-09-17  2:34 ` [PATCH net-next v2 2/3] selftests: nic_basic_tests: Add selftest case for speed and duplex state checks Mohan Prasad J
2024-09-18 12:38   ` Willem de Bruijn
2024-09-20  4:56     ` Mohan.Prasad
2024-09-17  2:34 ` [PATCH net-next v2 3/3] selftests: nic_basic_tests: Add selftest case for throughput check Mohan Prasad J

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=20240917023525.2571082-1-mohan.prasad@microchip.com \
    --to=mohan.prasad@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rosenp@gmail.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.com \
    /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