netdev - Re: [PATCH net-next 0/8] Hisilicon Network Subsystem 3 VF Ethernet 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: <CAJ3xEMgU2N8UStvXdQLL4jp-og-aiZbnzgJtvo+XxU2qu7S+aA@mail.gmail.com>
Date:   Sun, 3 Dec 2017 15:22:42 +0200
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     Salil Mehta <salil.mehta@...wei.com>
Cc:     David Miller <davem@...emloft.net>, yisen.zhuang@...wei.com,
        lipeng321@...wei.com, mehta.salil.lnk@...il.com,
        Linux Netdev List <netdev@...r.kernel.org>,
        Andy Gospodarek <andy@...yhouse.net>,
        Simon Horman <simon.horman@...ronome.com>,
        Jiri Pirko <jiri@...lanox.com>
Subject: Re: [PATCH net-next 0/8] Hisilicon Network Subsystem 3 VF Ethernet Driver

On Sun, Dec 3, 2017 at 2:32 PM, Salil Mehta <salil.mehta@...wei.com> wrote:
> This patch-set contains the support of the HNS3 (Hisilicon Network Subsystem 3)
> Virtual Function Ethernet driver for hip08 family of SoCs. The Physical Function
> driver is already part of the Linux mainline.
>
> This VF driver has its Hardware Compatibility Layer and has commom/unified ENET
> layer/client/ethtool code with the PF driver. The basic architecture of VF driver
> is derivative of the PF driver. Just like PF driver, this driver is also PCI
> Express based.


Hi,

I wasn't sure if/what PF side control plane user space APIs are
supported by this series,
can you elaborate on that?  Please note that since 4.8, the kernel
supports switchdev
mode for SRIOV drivers and it's highly desirable for new drivers to
support that. The old
mode (called legacy) is inferior in functionality and design. We
didn't do a clear statement
asking new drivers not to support the legacy mode, but still, it would
be good to support
the new mode from day one.

Or.