From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
To: dev@dpdk.org
Cc: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] doc: add port representor update in release notes
Date: Mon, 28 May 2018 17:12:21 +0100 [thread overview]
Message-ID: <20180528161222.18935-1-mohammad.abdul.awal@intel.com> (raw)
Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
---
doc/guides/rel_notes/release_18_05.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_05.rst b/doc/guides/rel_notes/release_18_05.rst
index e8d74f507..511d51908 100644
--- a/doc/guides/rel_notes/release_18_05.rst
+++ b/doc/guides/rel_notes/release_18_05.rst
@@ -313,6 +313,16 @@ New Features
on eth devices (right now only via SW RX/TX callbacks).
It also adds dependency on libelf.
+* **Added support for port representors.**
+
+ The DPDK port representors (also known as "VF representors" in the specific
+ context of VFs), which are to DPDK what the Ethernet switch device driver
+ model (**switchdev**) is to Linux, and which can be thought as a software
+ "patch panel" front-end for applications. DPDK port representors are
+ implemented as additional virtual Ethernet device (**ethdev**) instances,
+ spawned on an as needed basis through configuration parameters passed to the
+ driver of the underlying device using devargs.
+
API Changes
-----------
--
2.17.0
next reply other threads:[~2018-05-28 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 16:12 Mohammad Abdul Awal [this message]
2018-05-28 16:12 ` [dpdk-dev] [PATCH 2/2] doc: add vxlan and nvgre tunnel " Mohammad Abdul Awal
2018-05-28 16:52 ` Mcnamara, John
2018-05-29 10:31 ` Thomas Monjalon
2018-05-28 16:52 ` [dpdk-dev] [PATCH 1/2] doc: add port representor " Mcnamara, John
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 16:08 Mohammad Abdul Awal
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=20180528161222.18935-1-mohammad.abdul.awal@intel.com \
--to=mohammad.abdul.awal@intel.com \
--cc=dev@dpdk.org \
/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).