DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Boule <ivan.boule@6wind.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com, john.mcnamara@intel.com, thomas@monjalon.net
Subject: [dpdk-dev] [PATCH] doc: announce API change for ethdev port info
Date: Mon, 16 Oct 2017 16:27:47 +0200	[thread overview]
Message-ID: <1508164067-22952-1-git-send-email-ivan.boule@6wind.com> (raw)

To help administrative tasks on ports, new per-port information need
to be added into the data structure rte_eth_dev_info supplied by the
dev_infos_get() function exported by a Poll Mode Driver.

See http://dpdk.org/ml/archives/dev/2017-September/074885.html for
details.

Signed-off-by: Ivan Boule <ivan.boule@6wind.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
---
 doc/guides/rel_notes/deprecation.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 52058f5..1430120 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -92,3 +92,11 @@ Deprecation Notices
   The non-"do-sig" versions of the hash tables will be removed
   (including the ``signature_offset`` parameter)
   and the "do-sig" versions renamed accordingly.
+
+* librte_ether: additional fields will be added into the ``rte_eth_dev_info``
+  structure in 18.02, breaking the API. These fields will contain:
+
+  - the set of supported link modes,
+  - the set of advertised link modes,
+  - the type of port connector,
+  - autonegotiation enabled or not.
-- 
2.1.4

             reply	other threads:[~2017-10-16 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 14:27 Ivan Boule [this message]
2017-11-14 23:50 ` Thomas Monjalon
2017-11-15  8:13   ` Olivier MATZ
2017-11-15 15:23     ` Thomas Monjalon
2018-02-13 13:15 ` Olivier Matz

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=1508164067-22952-1-git-send-email-ivan.boule@6wind.com \
    --to=ivan.boule@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=olivier.matz@6wind.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).