[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB43228D1A331E875D84C1FF68DCA30@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Tue, 19 Jan 2021 04:21:21 +0000
From: Parav Pandit <parav@...dia.com>
To: David Ahern <dsahern@...il.com>, Jason Wang <jasowang@...hat.com>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Stephen Hemminger <stephen@...workplumber.org>
CC: "mst@...hat.com" <mst@...hat.com>, Eli Cohen <elic@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
谢永吉 <xieyongji@...edance.com>
Subject: RE: [PATCH 0/7] Introduce vdpa management tool
Hi David,
> From: David Ahern <dsahern@...il.com>
> Sent: Wednesday, December 9, 2020 4:17 AM
>
> 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.
Sorry for my late reply. I missed your message until yesterday.
Thanks for the ack and inputs.
Yes, I migrated the iproute2/vdpa to use now uses the common code introduced by dcb tool.
Waiting for kernel side to finish.
Powered by blists - more mailing lists