DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Shahaf Shuler <shahafs@mellanox.com>,
	Asaf Penso <asafp@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [RFC] net: new vdpa PMD for Mellanox devices
Date: Thu, 15 Aug 2019 10:47:07 +0000	[thread overview]
Message-ID: <DB3PR0502MB4028B30BA6DC45A34921F340D2AC0@DB3PR0502MB4028.eurprd05.prod.outlook.com> (raw)

The last Mellanox adapters\SoCs support virtio operations to accelerate the vhost data path.

A new net PMD will be added to implement the vdpa driver requirements on top of Mellanox
devices support it like ConnectX6 and BlueField.

Points:

  *   The mlx5_vdpa PMD run on top of PCI devices VF and PF.
  *   The Mellanox PCI device can be configured ether to support ethdev device or to support vdpa device.
  *   An one physical device can contain ethdev VFs\PF driven by the mlx5 PMD and vdpa VFs\PF driven by the new mlx5_vdpa PMD parallelly.
  *   The  decision which driver should be selected to probe Mellanox PCI device should be taken by the user using the PCI device devargs.
  *   mlx5 and mlx5_vdpa depend in rdma-core lib so some code may be shared between them,

due that a new mlx5 common directory will be added in drivers/commom for code reusing.

  *   All the guest physical memory of the virtqs will be translated to the host physical memory by the HW.

                 reply	other threads:[~2019-08-15 10:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DB3PR0502MB4028B30BA6DC45A34921F340D2AC0@DB3PR0502MB4028.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=asafp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@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).