From: Jakub Kicinski <jakub.kicinski@netronome.com>
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@mellanox.com,
kwankhede@nvidia.com, alex.williamson@redhat.com,
vuhuong@mellanox.com, yuvalav@mellanox.com, kvm@vger.kernel.org
Subject: Re: [RFC net-next v1 0/3] Support mlx5 mediated devices in host
Date: Wed, 13 Mar 2019 15:08:04 -0700 [thread overview]
Message-ID: <20190313150804.3702ae47@cakuba.netronome.com> (raw)
In-Reply-To: <1552082876-60228-1-git-send-email-parav@mellanox.com>
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
Hi Parav!
Sorry for going quiet, I'm hoping to clarify the use cases and
the devlink part on the other thread with Jiri, and then come back
to implementation details.
> 3. rdma device with IB link layer and IPoIB netdev
> 4. rdma/RoCE device and a netdev
> 5. rdma device with multiple ports
next prev parent reply other threads:[~2019-03-13 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 22:07 [RFC net-next v1 0/3] Support mlx5 mediated devices in host Parav Pandit
2019-03-08 22:07 ` [RFC net-next v1 1/3] vfio/mdev: Inherit dma masks of parent device Parav Pandit
2019-03-08 22:32 ` Alex Williamson
2019-03-09 3:55 ` Parav Pandit
2019-03-08 22:07 ` [RFC net-next v1 2/3] net/mlx5: Add mdev sub device life cycle command support Parav Pandit
2019-03-08 22:07 ` [RFC net-next v1 3/3] net/mlx5: Add mdev driver to bind to mdev devices Parav Pandit
2019-03-13 22:08 ` Jakub Kicinski [this message]
2019-03-14 21:38 ` [RFC net-next v1 0/3] Support mlx5 mediated devices in host Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190313150804.3702ae47@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alex.williamson@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@mellanox.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=vuhuong@mellanox.com \
--cc=yuvalav@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).