From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH] doc: deprecate KNI ethtool support
Date: Mon, 18 Feb 2019 12:30:02 +0000 [thread overview]
Message-ID: <20190218123002.26908-1-ferruh.yigit@intel.com> (raw)
Remove KNI ethtool support.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
RFC Patch: https://patches.dpdk.org/patch/49025/
---
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 1b4fcb7e6..0491eeea1 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -75,3 +75,11 @@ Deprecation Notices
* crypto/aesni_mb: the minimum supported intel-ipsec-mb library version will be
changed from 0.49.0 to 0.52.0.
+
+* kni: remove KNI ethtool support. To clarify, this is not to remove the KNI,
+ but only to remove ethtool support of it that is disabled by default and
+ can be enabled via ``CONFIG_RTE_KNI_KMOD_ETHTOOL`` config option.
+ Existing KNI ethtool implementation is only supported by ``igb`` & ``ixgbe``
+ drivers, by using a copy of kernel drivers in DPDK. This model can't be extend
+ to all drivers in DPDK and it is too much effort to maintain kernel modules in DPDK.
+ As a result users won't be able to use ``ethtool`` via ``igb`` & ``ixgbe`` anymore.
--
2.20.1
next reply other threads:[~2019-02-18 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 12:30 Ferruh Yigit [this message]
2019-02-18 14:24 ` Neil Horman
2019-02-18 14:26 ` Igor Ryzhov
2019-02-18 14:42 ` Jerin Jacob Kollanukkaran
2019-02-18 18:56 ` Rami Rosen
2019-03-27 13:37 ` Thomas Monjalon
2019-03-27 13:37 ` 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=20190218123002.26908-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.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).