netdev - Re: [PATCH 0/7] Introduce vdpa management tool

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: <831884f7-365d-b974-0bc5-f72729add98f@gmail.com>
Date:   Tue, 8 Dec 2020 15:47:11 -0700
From:   David Ahern <dsahern@...il.com>
To:     Jason Wang <jasowang@...hat.com>, Parav Pandit <parav@...dia.com>,
        virtualization@...ts.linux-foundation.org,
        Stephen Hemminger <stephen@...workplumber.org>
Cc:     mst@...hat.com, elic@...dia.com, netdev@...r.kernel.org,
        谢永吉 <xieyongji@...edance.com>
Subject: Re: [PATCH 0/7] Introduce vdpa management tool

On 11/26/20 8:53 PM, Jason Wang wrote:
> 1. Where does userspace vdpa tool reside which users can use?
> Ans: vdpa tool can possibly reside in iproute2 [1] as it enables user to
> create vdpa net devices.

iproute2 package is fine with us, but there are some expectations:
syntax, command options and documentation need to be consistent with
other iproute2 commands (this thread suggests it will be but just being
clear), and it needs to re-use code as much as possible (e.g., json
functions). If there is overlap with other tools (devlink, dcb, etc),
you should refactor into common code used by all. Petr Machata has done
this quite a bit for dcb and is a good example to follow.