netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>, netdev@vger.kernel.org
Subject: Re: [PATCH v4 1/5] net: Introduce new feature setting ops
Date: Tue, 24 Jan 2012 15:30:02 +0000	[thread overview]
Message-ID: <1327419002.5400.27.camel@deadeye> (raw)
In-Reply-To: <1327413243.7231.12.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

On Tue, 2012-01-24 at 14:54 +0100, Eric Dumazet wrote:
> Le lundi 07 février 2011 à 19:39 +0000, Ben Hutchings a écrit :
> > On Thu, 2011-02-03 at 15:21 +0100, Michał Mirosław wrote:
> > > This introduces a new framework to handle device features setting.
> > > It consists of:
> > >   - new fields in struct net_device:
> > > 	+ hw_features - features that hw/driver supports toggling
> > > 	+ wanted_features - features that user wants enabled, when possible
> > >   - new netdev_ops:
> > > 	+ feat = ndo_fix_features(dev, feat) - API checking constraints for
> > > 		enabling features or their combinations
> > > 	+ ndo_set_features(dev) - API updating hardware state to match
> > > 		changed dev->features
> > >   - new ethtool commands:
> > > 	+ ETHTOOL_GFEATURES/ETHTOOL_SFEATURES: get/set dev->wanted_features
> > > 		and trigger device reconfiguration if resulting dev->features
> > > 		changed
> > > 	+ ETHTOOL_GSTRINGS(ETH_SS_FEATURES): get feature bits names (meaning)
> > > 
> > > Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> > Reviewed-by: Ben Hutchings <bhutchings@solarflare.com>
> > 
> 
> 
> Hi guys
> 
> Do we have any ethtool patch to use these 'new' features ?

I have some unfinished changes to support this.  What I don't want to do
is to add an entirely separate set of options; I want -k/-K to work with
old and new kernel versions, supporting named features as an extension
where available.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2012-01-24 15:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 14:21 [PATCH v4 0/5] net: Unified offload configuration Michał Mirosław
2011-02-03 14:21 ` [PATCH v4 2/5] net: ethtool: use ndo_fix_features for offload setting Michał Mirosław
2011-02-07 21:01   ` David Miller
2011-02-03 14:21 ` [PATCH v4 3/5] net: use ndo_fix_features for ethtool_ops->set_flags Michał Mirosław
2011-02-07 19:46   ` Ben Hutchings
2011-02-07 21:03     ` David Miller
2011-02-03 14:21 ` [PATCH v4 1/5] net: Introduce new feature setting ops Michał Mirosław
2011-02-07 19:39   ` Ben Hutchings
2011-02-07 20:51     ` David Miller
2011-02-07 20:55       ` David Miller
2012-01-24 13:54     ` Eric Dumazet
2012-01-24 15:30       ` Ben Hutchings [this message]
2012-01-24 15:47         ` Eric Dumazet
2012-01-24 19:05         ` Michał Mirosław
2012-01-28  8:30           ` [RFC PATCH] ethtool: implement [GS]FEATURES handling Michał Mirosław
2012-01-28  8:37             ` [RFC PATCH v2] " Michał Mirosław
2012-01-28 10:02               ` Eric Dumazet
2011-02-03 14:21 ` [PATCH v4 5/5] loopback: convert to hw_features Michał Mirosław
2011-02-07 21:18   ` David Miller
2011-02-03 14:21 ` [PATCH v4 4/5] net: introduce NETIF_F_RXCSUM Michał Mirosław
2011-02-07 21:12   ` David Miller
2011-02-03 14:21 ` [PATCH v2] ethtool: implement G/SFEATURES calls Michał Mirosław
2011-02-07 21:37 ` [PATCH v4 0/5] net: Unified offload configuration David Miller
2011-02-07 22:49   ` Michał Mirosław
2011-02-07 22:52     ` David Miller
2011-02-07 23:12       ` Michał Mirosław
2011-02-08 19:40   ` David Miller
2011-02-08 23:55     ` Michał Mirosław
2011-02-08 23:58       ` David Miller

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=1327419002.5400.27.camel@deadeye \
    --to=bhutchings@solarflare.com \
    --cc=eric.dumazet@gmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --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).