mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Mohan.Prasad@microchip.com>
To: <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<kuba@kernel.org>, <shuah@kernel.org>,
	<Bryan.Whitehead@microchip.com>, <UNGLinuxDriver@microchip.com>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
	<horms@kernel.org>, <brett.creeley@amd.com>, <rosenp@gmail.com>
Subject: RE: [PATCH net-next 0/3] lan743x: This series of patches are for lan743x driver testing
Date: Mon, 9 Sep 2024 06:42:54 +0000	[thread overview]
Message-ID: <DM6PR11MB4236A76EB9FF90303153A83083992@DM6PR11MB4236.namprd11.prod.outlook.com> (raw)
In-Reply-To: <96e017b8-3702-4b39-a44f-91c8b4ebec89@lunn.ch>

Hello Andrew,

Thank you very much for the feedback and the brief explanation.

> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
> 
> On Fri, Sep 06, 2024 at 06:45:53AM +0000, Mohan.Prasad@microchip.com
> wrote:
> > Hello Andrew,
> >
> > Thank you for your review comments.
> >
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > > know the content is safe
> > >
> > > On Wed, Sep 04, 2024 at 03:45:46AM +0530, Mohan Prasad J wrote:
> > > > This series of patches are for testing the lan743x network driver.
> > > > Testing comprises autonegotiation, speed, duplex and throughput
> checks.
> > > > Tools such as ethtool, iperf3 are used in the testing process.
> > > > Performance test is done for TCP streams at different speeds.
> > >
> > > What is specific to lan743x? Why won't the autoneg test work for any
> > > interface which says it supports autoneg? Is duplex somehow special
> > > on the lan743x?
> > >
> > > Where possible, please try to make these tests generic, usable on
> > > any NIC. Or clearly document why they cannot be generic.
> > >
> >
> > As suggested, I will change the testcases to generic form and document
> them accordingly in the next version.
> 
> Great.
> 
> How much time do you have?
> 
> ethtool eth0
> Settings for eth0:
>         Supported ports: [ TP    MII ]
>         Supported link modes:   10baseT/Half 10baseT/Full
>                                 100baseT/Half 100baseT/Full
>                                 1000baseT/Half 1000baseT/Full
>         Supported pause frame use: Symmetric Receive-only
>         Supports auto-negotiation: Yes
>         Supported FEC modes: Not reported
>         Advertised link modes:  10baseT/Half 10baseT/Full
>                                 100baseT/Half 100baseT/Full
>                                 1000baseT/Half 1000baseT/Full
>         Advertised pause frame use: Symmetric Receive-only
>         Advertised auto-negotiation: Yes
>         Advertised FEC modes: Not reported
>         Link partner advertised link modes:  10baseT/Half 10baseT/Full
>                                              100baseT/Half 100baseT/Full
>                                              1000baseT/Full
> 
> You can see that both the local device and the peer support auto-neg. You
> can see what link modes both the local and peer supports. The local device
> has 1000BaseT/Half where the peer does not, which is reasonably common.
> So you could use this as a basis for the test, ensurer 5 link modes do pass
> auto-neg, and one fails.
> 
> If you can, please try to avoid hard coding any link modes. There will be some
> data centre NICs with a lowest speed to 10GBaseX, for example.
> There are some automotive devices with 10BaseT-1L which does not support
> autp-neg etc. It would be nice if the test could be used on any interface and
> the test will decide itself what can be tested, or if it should skip everything?
> 
> And by the way, thanks for working on tests. We need more people like you
> contributing to them.
> 

I am currently working on this and would rework as soon as possible.
The feedback that you provided is highly helpful and I will remodel the implementation with these points in mind.
Hopefully you can see that in the next version.

>         Andrew

  reply	other threads:[~2024-09-09  6:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 22:15 Mohan Prasad J
2024-09-03 22:15 ` [PATCH net-next 1/3] selftests: lan743x: Add testfile for lan743x network driver Mohan Prasad J
2024-09-04 16:10   ` Brett Creeley
2024-09-06  6:54     ` Mohan.Prasad
2024-09-03 22:15 ` [PATCH net-next 2/3] selftests: lan743x: Add testcase to check speed and duplex state of lan743x Mohan Prasad J
2024-09-04 16:05   ` Brett Creeley
2024-09-06  6:52     ` Mohan.Prasad
2024-09-03 22:15 ` [PATCH net-next 3/3] selftests: lan743x: Add testcase to check throughput " Mohan Prasad J
2024-09-04 16:15   ` Brett Creeley
2024-09-06  6:56     ` Mohan.Prasad
2024-09-04  5:30 ` [PATCH net-next 0/3] lan743x: This series of patches are for lan743x driver testing Andrew Lunn
2024-09-06  6:45   ` Mohan.Prasad
2024-09-06 12:08     ` Andrew Lunn
2024-09-09  6:42       ` Mohan.Prasad [this message]
2024-09-09 13:24         ` Andrew Lunn

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=DM6PR11MB4236A76EB9FF90303153A83083992@DM6PR11MB4236.namprd11.prod.outlook.com \
    --to=mohan.prasad@microchip.com \
    --cc=Bryan.Whitehead@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 \
    /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

all inboxes | Powered by JetHome®