From: David Miller <davem@davemloft.net>
To: ecree@solarflare.com
Cc: linux-net-drivers@solarflare.com, netdev@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: [PATCH RESEND net-next 0/2] ntuple filters with RSS
Date: Wed, 07 Mar 2018 10:24:15 -0500 (EST) [thread overview]
Message-ID: <20180307.102415.1350852471214942248.davem@davemloft.net> (raw)
In-Reply-To: <3d8f5254-84e2-bb13-f4ae-f4951cbce55c@solarflare.com>
From: Edward Cree <ecree@solarflare.com>
Date: Fri, 2 Mar 2018 16:01:47 +0000
> On 01/03/18 18:36, David Miller wrote:
>> We really should have the ethtool interfaces under deep freeze until we
>> convert it to netlink or similar.
>> Second, this is a real hackish way to extend ethtool with new
>> semantics.� A structure changes layout based upon a flag bit setting
>> in an earlier member?� Yikes...
> Yeah, while I'm reasonably confident it's ABI-compatible (presence of that
> �flag in the past should always have led to drivers complaining they didn't
> �recognise it), and it is somewhat similar to the existing FLOW_EXT flag,
> �it is indeed rather ugly.� This is the only way I could see to do it
> �without adding a whole new command number, which I felt might also be
> �contentious (see: deep freeze) but is probably a better approach.
>
>> Lastly, there has been feedback asking how practical and useful this
>> facility actually is, and you must address that.
> According to our marketing folks, there is end-user demand for this feature
> �or something like it.� I didn't see any arguments why this isn't useful,
> �just that other things might be useful too.� (Also, sorry it took me so
> �long to address their feedback, but I had to do a bit of background
> �reading before I could understand what Jakub was suggesting.)
Ok.
Since nobody is really working on the ethtool --> devlink/netlink conversion,
it really isn't reasonable for me to block useful changes like your's.
So please resubmit this series and I will apply it.
Thanks.
next prev parent reply other threads:[~2018-03-07 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 17:59 [PATCH RESEND net-next 0/2] ntuple filters with RSS Edward Cree
2018-02-27 18:02 ` [PATCH net-next 1/2] net: ethtool: extend RXNFC API to support RSS spreading of filter matches Edward Cree
2018-02-27 18:03 ` [PATCH net-next 2/2] sfc: support RSS spreading of ethtool ntuple filters Edward Cree
2018-03-01 20:51 ` kbuild test robot
2018-02-27 23:47 ` [PATCH RESEND net-next 0/2] ntuple filters with RSS Jakub Kicinski
2018-02-28 1:24 ` Alexander Duyck
2018-03-02 15:24 ` Edward Cree
2018-03-02 18:55 ` Jakub Kicinski
2018-03-02 23:24 ` Alexander Duyck
2018-03-01 18:36 ` David Miller
2018-03-02 16:01 ` Edward Cree
2018-03-02 17:49 ` David Riddoch
2018-03-07 15:24 ` David Miller [this message]
2018-03-07 15:40 ` Edward Cree
2018-03-07 20:55 ` David Miller
[not found] <533b5eff-49b6-16c3-9873-dda3fb05c3d4@solarflare.com>
2018-02-27 17:38 ` David Miller
2018-02-27 17:55 ` Edward Cree
2018-02-27 19:28 ` John W. Linville
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=20180307.102415.1350852471214942248.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).