From: Dan Gora <dg@adax.com>
To: dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, Dan Gora <dg@adax.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add kni changes to release note
Date: Mon, 5 Nov 2018 16:29:34 -0200 [thread overview]
Message-ID: <20181105182934.20599-1-dg@adax.com> (raw)
Add the new module parameter for the KNI kernel module, the new command
line flag for the KNI sample application, and the new API function
'rte_kni_update_link()' to the release note.
Signed-off-by: Dan Gora <dg@adax.com>
---
doc/guides/rel_notes/release_18_11.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_11.rst b/doc/guides/rel_notes/release_18_11.rst
index cfa92b8c0..43fe849db 100644
--- a/doc/guides/rel_notes/release_18_11.rst
+++ b/doc/guides/rel_notes/release_18_11.rst
@@ -301,6 +301,16 @@ New Features
computation to the NIST Cryptographic Algorithm Validation Program (CAVP)
test vectors.
+* **Updated KNI kernel module and sample application.**
+
+ Updated the KNI kernel module with a new kernel module parameter,
+ ``carrier=[on|off]`` to allow the user to control the default carrier
+ state of KNI kernel network interfaces.
+
+ Added a new command line flag ``-m`` to the KNI sample application to
+ monitor and automatically reflect the physical NIC carrier state to the
+ KNI kernel network interface with the new ``rte_kni_update_link()`` API.
+
API Changes
-----------
@@ -362,6 +372,9 @@ API Changes
and seen as invalid because of its state ``RTE_ETH_DEV_UNUSED``.
This new behaviour is enabled per driver for a migration period.
+* kni: Added the new API function ``rte_kni_update_link()`` to allow the user
+ to set the carrier state of the KNI kernel network interface.
+
* A new device flag, RTE_ETH_DEV_NOLIVE_MAC_ADDR, changes the order of
actions inside rte_eth_dev_start regarding MAC set. Some NICs do not
support MAC changes once the port has started and with this new device
--
2.19.0
next reply other threads:[~2018-11-05 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 18:29 Dan Gora [this message]
2018-11-05 19:06 ` Ferruh Yigit
2018-11-05 19:27 ` Dan Gora
2018-11-05 19:54 ` [dpdk-dev] [PATCH v2] " Dan Gora
2018-11-14 0:34 ` Ferruh Yigit
2018-11-18 23:17 ` 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=20181105182934.20599-1-dg@adax.com \
--to=dg@adax.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).