linux-kernel - Re: [PATCH net-next v4 3/3] selftests: nic_performance: Add selftest for performance of NIC driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <554d8684-7eec-4379-9a21-0b4a562358be@redhat.com>
Date: Tue, 19 Nov 2024 11:12:16 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Mohan Prasad J <mohan.prasad@...rochip.com>, netdev@...r.kernel.org,
 davem@...emloft.net, kuba@...nel.org, andrew@...n.ch
Cc: edumazet@...gle.com, shuah@...nel.org, linux-kernel@...r.kernel.org,
 linux-kselftest@...r.kernel.org, horms@...nel.org, brett.creeley@....com,
 rosenp@...il.com, UNGLinuxDriver@...rochip.com, willemb@...gle.com,
 petrm@...dia.com
Subject: Re: [PATCH net-next v4 3/3] selftests: nic_performance: Add selftest
 for performance of NIC driver

On 11/14/24 20:25, Mohan Prasad J wrote:
> +#Setup:
> +#Connect the DUT PC with NIC card to partner pc back via ethernet medium of your choice(RJ45, T1)
> +#
> +#        DUT PC                                              Partner PC
> +#┌───────────────────────┐                         ┌──────────────────────────┐
> +#│                       │                         │                          │
> +#│                       │                         │                          │
> +#│           ┌───────────┐                         │                          │
> +#│           │DUT NIC    │         Eth             │                          │
> +#│           │Interface ─┼─────────────────────────┼─    any eth Interface    │
> +#│           └───────────┘                         │                          │
> +#│                       │                         │                          │
> +#│                       │                         │                          │
> +#└───────────────────────┘                         └──────────────────────────┘
> +#
> +#Configurations:
> +#To prevent interruptions, Add ethtool, ip to the sudoers list in remote PC and get the ssh key from remote.
> +#Required minimum ethtool version is 6.10
> +#Change the below configuration based on your hw needs.
> +# """Default values"""
> +#time_delay = 8 #time taken to wait for transitions to happen, in seconds.
> +#test_duration = 10  #performance test duration for the throughput check, in seconds.
> +#send_throughput_threshold = 80 #percentage of send throughput required to pass the check
> +#receive_throughput_threshold = 50 #percentage of receive throughput required to pass the check

Very likely we will have to tune the thresholds and possibly make them
dependent on the H/W and S/W setup (Kconf), but overall I think it makes
sense as a first step.

Thanks,

Paolo