[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201116145226.27b30b1f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Mon, 16 Nov 2020 14:52:26 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Parav Pandit <parav@...dia.com>
Cc: <netdev@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
<gregkh@...uxfoundation.org>, <jiri@...dia.com>, <jgg@...dia.com>,
<dledford@...hat.com>, <leonro@...dia.com>, <saeedm@...dia.com>,
<davem@...emloft.net>
Subject: Re: [PATCH net-next 00/13] Add mlx5 subfunction support
On Thu, 12 Nov 2020 21:24:10 +0200 Parav Pandit wrote:
> This series introduces support for mlx5 subfunction (SF).
> A subfunction is a portion of a PCI device that supports multiple
> classes of devices such as netdev, RDMA and more.
>
> This patchset is based on Leon's series [3].
> It is a third user of proposed auxiliary bus [4].
>
> Subfunction support is discussed in detail in RFC [1] and [2].
> RFC [1] and extension [2] describes requirements, design, and proposed
> plumbing using devlink, auxiliary bus and sysfs for systemd/udev
> support.
So we're going to have two ways of adding subdevs? Via devlink and via
the new vdpa netlink thing?
Question number two - is this supposed to be ready to be applied to
net-next? It seems there is a conflict.
Also could you please wrap your code at 80 chars?
Thanks.
Powered by blists - more mailing lists