Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Parav Pandit <parav@mellanox.com>
To:     Jakub Kicinski <jakub.kicinski@netronome.com>
CC:     "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "michal.lkml@markovi.net" <michal.lkml@markovi.net>,
        "davem@davemloft.net" <davem@davemloft.net>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
        Jiri Pirko <jiri@mellanox.com>,
        "kwankhede@nvidia.com" <kwankhede@nvidia.com>,
        "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
        Vu Pham <vuhuong@mellanox.com>,
        Yuval Avnery <yuvalav@mellanox.com>,
        "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: RE: [RFC net-next v1 0/3] Support mlx5 mediated devices in host
Thread-Topic: [RFC net-next v1 0/3] Support mlx5 mediated devices in host
Thread-Index: AQHU1ftxoq/20NoyU02DSUADWZ4DWKYKJn4AgAGFZKA=
Date:   Thu, 14 Mar 2019 21:38:53 +0000
Message-ID: <VI1PR0501MB2271E31103727546484AB834D14B0@VI1PR0501MB2271.eurprd05.prod.outlook.com>
References: <1552082876-60228-1-git-send-email-parav@mellanox.com>
 <20190313150804.3702ae47@cakuba.netronome.com>
In-Reply-To: <20190313150804.3702ae47@cakuba.netronome.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: mellanox.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d832070e-6651-4dde-0cf8-08d6a8c57496
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2019 21:38:53.1072
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB2399
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Jakub,

> -----Original Message-----
> From: Jakub Kicinski <jakub.kicinski@netronome.com>
> Sent: Wednesday, March 13, 2019 5:08 PM
> To: Parav Pandit <parav@mellanox.com>
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org;
> michal.lkml@markovi.net; davem@davemloft.net;
> gregkh@linuxfoundation.org; Jiri Pirko <jiri@mellanox.com>;
> kwankhede@nvidia.com; alex.williamson@redhat.com; Vu Pham
> <vuhuong@mellanox.com>; Yuval Avnery <yuvalav@mellanox.com>;
> kvm@vger.kernel.org
> Subject: Re: [RFC net-next v1 0/3] Support mlx5 mediated devices in host
>=20
> On Fri,  8 Mar 2019 16:07:53 -0600, Parav Pandit wrote:
> > Use case:
> > ---------
> > A user wants to create/delete hardware linked sub devices without
> > using SR-IOV.
> > These devices for a pci device can be netdev (optional rdma device) or
> > other devices. Such sub devices share some of the PCI device resources
> > and also have their own dedicated resources.
> > A user wants to use this device in a host where PF PCI device exist.
> > (not in a guest VM.) A user may want to use such sub device in future
> > in guest VM.
> >
> > Few examples are:
> > 1. netdev having its own txq(s), rq(s) and/or hw offload parameters.
> > 2. netdev with switchdev mode using netdev representor
>=20
> Hi Parav!
>=20
> Sorry for going quiet, I'm hoping to clarify the use cases and the devlin=
k part
> on the other thread with Jiri, and then come back to implementation detai=
ls.
>=20
That's fine. Now we have detached two things so we don't need to create med=
iated devices etc through devlink anymore.
It is not just implementation details here in RFC.
RFC describes the single and multiport use cases and attachment with devlin=
k too.
It uses existing well defined devlink objects.
So I am not envisioning a big change.

> > 3. rdma device with IB link layer and IPoIB netdev 4. rdma/RoCE device
> > and a netdev 5. rdma device with multiple ports