From: Shahaf Shuler <shahafs@mellanox.com>
To: nhorman@tuxdriver.com, thomas@monjalon.net
Cc: dev@dpdk.org, declan.doherty@intel.com,
mohammad.abdul.awal@intel.com, ferruh.yigit@intel.com,
remy.horton@intel.com
Subject: [dpdk-dev] [PATCH] doc: announce ABI change to support VF representors
Date: Wed, 14 Feb 2018 14:32:44 +0200 [thread overview]
Message-ID: <20180214123244.50967-1-shahafs@mellanox.com> (raw)
This is following the RFC being discussed and targets 18.05
http://dpdk.org/ml/archives/dev/2018-January/085716.html
Cc: declan.doherty@intel.com
Cc: mohammad.abdul.awal@intel.com
Cc: ferruh.yigit@intel.com
Cc: remy.horton@intel.com
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d59ad5988..f6151de63 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -59,3 +59,9 @@ Deprecation Notices
be added between the producer and consumer structures. The size of the
structure and the offset of the fields will remain the same on
platforms with 64B cache line, but will change on other platforms.
+
+* ethdev: A work is being planned for 18.05 to expose VF port representors
+ as a mean to perform control and data path operation on the different VFs.
+ As VF representor is an ethdev port, new fields are needed in order to map
+ between the VF representor and the VF or the parent PF. Those new fields
+ are to be included in ``rte_eth_dev_info`` struct.
--
2.12.0
next reply other threads:[~2018-02-14 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 12:32 Shahaf Shuler [this message]
2018-02-14 13:50 ` Thomas Monjalon
2018-02-14 13:54 ` Doherty, Declan
2018-02-14 14:50 ` Remy Horton
2018-02-14 15:27 ` Boccassi, Luca
2018-02-14 15:54 ` Jerin Jacob
2018-02-14 16:50 ` Thomas Monjalon
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=20180214123244.50967-1-shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=remy.horton@intel.com \
--cc=thomas@monjalon.net \
/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).