From: Neil Horman <nhorman@tuxdriver.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Igor Ryzhov <iryzhov@nfware.com>
Subject: Re: [dpdk-dev] [PATCH v2] kni: remove ethtool support
Date: Fri, 24 May 2019 15:27:48 -0400 [thread overview]
Message-ID: <20190524192748.GA16369@hmswarspite.think-freely.org> (raw)
In-Reply-To: <20190524165521.9726-1-ferruh.yigit@intel.com>
On Fri, May 24, 2019 at 05:55:20PM +0100, Ferruh Yigit wrote:
> Current design requires kernel drivers and they need to be probed by
> Linux up to some level so that they can be usable by DPDK for ethtool
> support, this requires maintaining the Linux drivers in DPDK.
>
> Also ethtool support is limited and hard, if not impossible, to expand
> to other PMDs.
>
> Since KNI ethtool support is not used commonly, if not used at all,
> removing the support for the sake of simplicity and maintenance.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
next prev parent reply other threads:[~2019-05-24 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 1:25 [dpdk-dev] [RFC] " Ferruh Yigit
2018-12-18 8:20 ` Igor Ryzhov
2018-12-18 9:20 ` Ferruh Yigit
2018-12-18 18:17 ` Ferruh Yigit
2019-01-05 16:55 ` Igor Ryzhov
2019-02-06 13:12 ` Igor Ryzhov
2019-02-18 12:33 ` Ferruh Yigit
2019-02-18 13:07 ` Igor Ryzhov
2019-02-18 13:18 ` Ferruh Yigit
2019-05-24 16:29 ` [dpdk-dev] [PATCH] " Ferruh Yigit
2019-05-24 16:46 ` Stephen Hemminger
2019-05-24 16:46 ` Ferruh Yigit
2019-05-24 16:55 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2019-05-24 19:27 ` Neil Horman [this message]
2019-05-29 21:44 ` 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=20190524192748.GA16369@hmswarspite.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=iryzhov@nfware.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stephen@networkplumber.org \
--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).