[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB4322C97E73753786B179ACE3DC3F0@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Fri, 18 Sep 2020 20:09:24 +0000
From: Parav Pandit <parav@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next v2 0/8] devlink: Add SF add/delete devlink ops
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Friday, September 18, 2020 11:58 PM
>
> On Fri, 18 Sep 2020 17:47:24 +0000 Parav Pandit wrote:
> > > > What do you suggest?
> > >
> > > Start with real patches, not netdevsim.
> >
> > Hmm. Shall I split the series below, would that be ok?
> >
> > First patchset,
> > (a) devlink piece to add/delete port
> > (b) mlx5 counter part
> >
> > Second patchset,
> > (a) devlink piece to set the state
> > (b) mlx5 counter part
> >
> > Follow on patchset to create/delete sf's netdev on virtbus in mlx5 + devlink
> plumbing.
> > Netdevsim after that.
>
> I'd start from the virtbus part so we can see what's being created.
How do you reach there without a user interface?
Powered by blists - more mailing lists