netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: question about ethtool bits?
Date: Tue, 11 Nov 2014 18:12:49 +0000	[thread overview]
Message-ID: <1415729569.3398.104.camel@decadent.org.uk> (raw)
In-Reply-To: <20141110124718.00004efc@unknown>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

On Mon, 2014-11-10 at 12:47 -0800, Jesse Brandeburg wrote:
> Ben et al,
> 
> So, I was just looking at adding some more types/speeds to
> ethtool.h and noticed we are about out of bits in ecmd->advertising
> (and others), which are declared u32.
> 
> We currently have room for one more type (bit 31) and then all 32 bits
> will be full.

Right, I've been seeing this coming for a while.

[...]
> There are two u32's reserved at the end of ethtool_cmd.
> 
> Suggestions?

Any extension needs to be applied to all of advertising, supported and
lp_advertising.  So we could take 6 of the 8 reserved bytes and extend
them all by 16 bits.

Whoever does this should add getter/setter functions, as has been done
with the extension of speed.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
                                                         - Carolyn Scheppner

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2014-11-11 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 20:47 question about ethtool bits? Jesse Brandeburg
2014-11-11 18:12 ` Ben Hutchings [this message]

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=1415729569.3398.104.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=jesse.brandeburg@intel.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).