All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ethtool 2/3] ethtool: Regularise handling of offload flags
Date: Tue, 22 Feb 2011 16:44:33 +0000	[thread overview]
Message-ID: <1298393073.14956.1.camel@bwh-desktop> (raw)
In-Reply-To: <20110222145004.GB25132@rere.qmqm.pl>

On Tue, 2011-02-22 at 15:50 +0100, Michał Mirosław wrote:
> On Mon, Feb 21, 2011 at 04:59:08PM +0000, Ben Hutchings wrote:
> > Use the new ETHTOOL_{G,S}FEATURES operations where available, and
> > use the new structure and netif feature flags in any case.
> > 
> > Replace repetitive code for getting/setting offload flags with data-
> > driven loops.
> > 
> > This changes error messages to use the same long names for offload
> > flags as in dump_offload(), and changes various exit codes to 1.
> > 
> > Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
> > ---
> > NEITF_F_* flags are copied into ethtool-util.h for now.  I think in
> > future they should be exposed from <linux/netdevice.h> (hence the
> > #ifndef).
> 
> I tried to avoid making NETIF_F_ flags an ABI. That's why there's new
> ETH_SS_FEATURES ethtool string set. When bits in features get used up
> it might be desirable to reorder them while introducing a new field
> in struct net_device (eg. move non-changeable bits out of features).

The order is unimportant.  And feature flags are already exposed through
sysfs, so they are part of the kernel ABI.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
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:[~2011-02-22 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 16:54 [PATCH ethtool 0/3] Regularise handling of offload flags Ben Hutchings
2011-02-21 16:57 ` [PATCH ethtool 1/3] ethtool-copy.h: sync with net-next-2.6 Ben Hutchings
2011-02-21 16:59 ` [PATCH ethtool 2/3] ethtool: Regularise handling of offload flags Ben Hutchings
2011-02-22 14:50   ` Michał Mirosław
2011-02-22 16:44     ` Ben Hutchings [this message]
2011-02-22 17:03       ` Michał Mirosław
2011-02-22 21:17   ` Michał Mirosław
2011-02-23  3:03   ` Michał Mirosław
2011-02-21 16:59 ` [PATCH ethtool 3/3] ethtool: Report additional offload flag changes made automatically Ben Hutchings

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=1298393073.14956.1.camel@bwh-desktop \
    --to=bhutchings@solarflare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.