From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Michal Kubecek <mkubecek@suse.cz>, <netdev@vger.kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
David Miller <davem@redhat.com>,
Jakub Jelinek <jj@ultra.linux.cz>,
Jeff Garzik <jgarzik@pobox.com>, Tim Hockin <thockin@sun.com>,
Eli Kupermann <eli.kupermann@intel.com>,
Chris Leech <christopher.leech@intel.com>,
Scott Feldman <scott.feldman@intel.com>,
"Ben Hutchings" <ben@decadent.org.uk>,
Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: [RFC] ethtool: Support for driver private ioctl's
Date: Fri, 6 Apr 2018 14:57:26 +0100 [thread overview]
Message-ID: <c9e4f4a4-bf58-6272-943e-5eeadeefdaa9@synopsys.com> (raw)
In-Reply-To: <20180406090702.mgzozmkkh3vuhe7w@unicorn.suse.cz>
Hi Michal,
On 06-04-2018 10:07, Michal Kubecek wrote:
> On Thu, Apr 05, 2018 at 08:50:49AM -0700, Florian Fainelli wrote:
>> On 04/05/2018 03:47 AM, Jose Abreu wrote:
>>> Background: Synopsys Ethernet IP's have a certain number of
>>> features which can be reconfigured at runtime. Giving you two
>>> examples: One of the most recent one is the safety features,
>>> which can be enabled/disabled and forced at runtime. Another one
>>> is a Flexible RX Parser which can route specific packets to
>>> specific RX DMA channels. Given that these are features specific
>>> to our IP's it would not be useful to add an uniform API for this
>>> because the users would only be one or two drivers ...
>> Parsing of packets and directing the matched packets to specific
>> queues/channels can be done through ethtool rxnfc API, tc/cls_flower as
>> well, so you should really check whether those APIs don't already allow
>> you to do what you want.
>>
>> ethtool already supports a concept of private flags, not ioctl() though
>> which allows you to toggle boolean values for instance (or technically
>> up to how many bits a "flag" is used to represent) is that enough or do
>> you need to turn on/off the feature as well as pass configuration
>> parameters?
> Perhaps introducing "driver/device specific tunables" (i.e. something
> like tunables or PHY tunables but specific to a particular device) could
> be a way. But it could get out of control quickly and users wouldn't be
> happy if they had to set the same (or almost the same) parameter under
> five different names for five NIC vendors.
Yeah, that wouldn't be good but I think this should be a
responsibility to developer: To see if there is an existing
API/ethtool entry before implementing the "tunable". I think a
big concern, for me at least, is that ethtool already has a lot
of options and introducing even more would lead the user to
confusion ...
Thanks and Best Regards,
Jose Miguel Abreu
>
> Michal Kubecek
next prev parent reply other threads:[~2018-04-06 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 10:47 [RFC] ethtool: Support for driver private ioctl's Jose Abreu
2018-04-05 15:50 ` Florian Fainelli
2018-04-06 9:07 ` Michal Kubecek
2018-04-06 13:57 ` Jose Abreu [this message]
2018-04-06 13:51 ` Jose Abreu
2018-04-06 14:47 ` Andrew Lunn
2018-04-06 14:51 ` Jose Abreu
2018-04-07 19:58 ` Florian Fainelli
2018-04-24 9:37 ` Jose Abreu
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=c9e4f4a4-bf58-6272-943e-5eeadeefdaa9@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=ben@decadent.org.uk \
--cc=christopher.leech@intel.com \
--cc=davem@redhat.com \
--cc=eli.kupermann@intel.com \
--cc=f.fainelli@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jj@ultra.linux.cz \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=scott.feldman@intel.com \
--cc=thockin@sun.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