From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>, Dan Gora <dg@adax.com>
Subject: [dpdk-dev] [PATCH] doc: update release notes for default KNI carries status
Date: Mon, 5 Nov 2018 17:28:44 +0000 [thread overview]
Message-ID: <20181105172844.72228-1-ferruh.yigit@intel.com> (raw)
Commit 89397a01ce4a ("kni: set default carrier state of interface")
changes the KNI interface default carrier status. Which prevents traffic
flow by default and may break some existing usage / testing.
Document this behavior change in release notes.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Cc: Dan Gora <dg@adax.com>
---
doc/guides/rel_notes/release_18_11.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_11.rst b/doc/guides/rel_notes/release_18_11.rst
index 6ce276b22..69c4d1bf6 100644
--- a/doc/guides/rel_notes/release_18_11.rst
+++ b/doc/guides/rel_notes/release_18_11.rst
@@ -383,6 +383,13 @@ API Changes
This means ``ethtool "-a|--show-pause", "-s|--change"`` won't work, and
``ethtool <iface>`` output will have less information.
+* KNI, by default interface carrier status is ``off`` which means there won't be any traffic.
+ It can be set to ``on`` via ``rte_kni_update_link()`` API or via ``sysfs`` interface:
+ ``echo 1 > /sys/class/net/vEth0/carrier``. Note interface should be ``up`` to be able
+ to read/write sysfs interface.
+ When KNI sample application is used ``-m`` parameter can be used to automatically update
+ the carrier status for the interface.
+
ABI Changes
-----------
--
2.17.2
next reply other threads:[~2018-11-05 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:28 Ferruh Yigit [this message]
2018-11-05 18:12 ` Dan Gora
2018-11-05 18:21 ` Ferruh Yigit
2018-11-05 18:23 ` Dan Gora
2018-11-05 18:34 ` Dan Gora
2018-11-18 23:24 ` 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=20181105172844.72228-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dg@adax.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).