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]
Date:   Wed, 3 Jun 2020 11:12:51 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Danielle Ratson <danieller@...lanox.com>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, michael.chan@...adcom.com, kuba@...nel.org,
        jeffrey.t.kirsher@...el.com, saeedm@...lanox.com, leon@...nel.org,
        jiri@...lanox.com, idosch@...lanox.com, snelson@...sando.io,
        drivers@...sando.io, andrew@...n.ch, vivien.didelot@...il.com,
        mlxsw@...lanox.com, Petr Machata <petrm@...lanox.com>
Subject: Re: [RFC PATCH net-next 8/8] selftests: net: Add port split test



On 6/2/2020 4:31 AM, Danielle Ratson wrote:
> Test port split configuration using previously added number of port lanes
> attribute.
> 
> Check that all the splittable ports are successfully split to their maximum
> number of lanes and below, and that those which are not splittable fail to
> be split.
> 
> Test output example:
> 
> TEST: swp4 is unsplittable                                         [ OK ]
> TEST: split port swp53 into 4                                      [ OK ]
> TEST: Unsplit port pci/0000:03:00.0/25                             [ OK ]
> TEST: split port swp53 into 2                                      [ OK ]
> TEST: Unsplit port pci/0000:03:00.0/25                             [ OK ]
> 
> Signed-off-by: Danielle Ratson <danieller@...lanox.com>
> Reviewed-by: Petr Machata <petrm@...lanox.com>
> ---
>  tools/testing/selftests/net/Makefile          |   1 +
>  .../selftests/net/devlink_port_split.py       | 259 ++++++++++++++++++

Any reason why this is written in python versus shell?
-- 
Florian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ