netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Ayyappan Veeraiyan <ayyappan.veeraiyan@intel.com>,
	netdev@vger.kernel.org, auke-jan.h.kok@intel.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH] ixgbe: Introduce new 10GbE driver for Intel 82598 based PCI	Express adapters...
Date: Mon, 02 Jul 2007 10:25:49 -0400	[thread overview]
Message-ID: <46890AED.7070906@garzik.org> (raw)
In-Reply-To: <4689062A.8080809@linux.intel.com>

Arjan van de Ven wrote:
>  >> +    u32 alloc_rx_buff_failed;
>>> +    struct {
>>> +        unsigned int rx_csum_enabled    :1;
>>> +        unsigned int msi_capable    :1;
>>> +        unsigned int msi_enabled    :1;
>>> +        unsigned int msix_capable    :1;
>>> +        unsigned int msix_enabled    :1;
>>> +        unsigned int imir_enabled    :1;
>>> +        unsigned int in_netpoll        :1;
>>> +    } flags;
>>
>> always avoid bitfields.  They generate horrible code, and endian 
>> problems abound (though no endian problems are apparent here).
> 
> they generate no worse code than open coding the checks for these 
> feature flags...

That would be the logical assumption, but reality does not bear that 
logic out to be true.

I'm not sure whether gcc is confused about ABI alignment or such, on 
various platforms, but every time I look at the asm generated it is 
/not/ equivalent to open-coded feature flags and bitwise logic.  Often 
it is demonstrably worse.

The same is true for icc too :)  Bitfields are just bad juju for 
compilers, I guess.

	Jeff




  reply	other threads:[~2007-07-02 14:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 23:44 [ANNOUNCE] new driver ixgbe for Intel(R) 10GbE PCI Express adapters Ayyappan.Veeraiyan
2007-06-12 23:44 ` [PATCH] ixgbe: Introduce new 10GbE driver for Intel 82598 based " Ayyappan Veeraiyan
2007-07-02 12:52   ` Jeff Garzik
2007-07-02 14:05     ` Arjan van de Ven
2007-07-02 14:25       ` Jeff Garzik [this message]
2007-07-02 14:27         ` Arjan van de Ven
2007-07-02 14:41           ` Jeff Garzik
2007-07-02 14:41             ` Arjan van de Ven
2007-07-02 15:26             ` Kok, Auke
2007-07-02 15:32               ` Jeff Garzik
2007-07-02 15:52                 ` Andrew Morton
2007-07-02 16:09                   ` Jeff Garzik
2007-07-02 15:54                 ` Kok, Auke
2007-07-06  8:46                   ` Ingo Oeser
2007-07-02 14:31         ` Arjan van de Ven
2007-07-02 19:00     ` Veeraiyan, Ayyappan
2007-07-02 19:04       ` Ayyappan Veeraiyan
2007-07-02 20:16       ` Christoph Hellwig
2007-07-02 21:09       ` Stephen Hemminger
2007-07-02 21:42         ` Christoph Hellwig
2007-07-02 22:02           ` Kok, Auke
2007-07-02 22:08             ` Jeff Garzik
2007-07-02 22:10             ` Michael Buesch
2007-07-02 22:16               ` Jeff Garzik
2007-07-02 23:57                 ` Kok, Auke
2007-07-03  0:11                   ` Jeff Garzik
2007-07-03  0:16                   ` Inaky Perez-Gonzalez
2007-07-03 13:19                     ` Jeff Garzik
2007-07-03 18:24                       ` Inaky Perez-Gonzalez
2007-07-05 23:29                         ` Jeff Garzik
2007-07-03  0:08           ` Veeraiyan, Ayyappan
2007-07-03 22:01             ` Ayyappan Veeraiyan
2007-07-02 22:56         ` Veeraiyan, Ayyappan
2007-07-03 12:53       ` Neil Horman
2007-07-05 12:37         ` Neil Horman
2007-07-09 14:21           ` Veeraiyan, Ayyappan
2007-07-10  0:57             ` Neil Horman
2007-06-13 23:05 ` [ANNOUNCE] new driver ixgbe for Intel(R) 10GbE " Francois Romieu
2007-06-13 23:18   ` Kok, Auke
2007-06-14  0:06   ` Ayyappan Veeraiyan
2007-06-14 20:36     ` Francois Romieu

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=46890AED.7070906@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=ayyappan.veeraiyan@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).