netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: zbr@ioremap.net, netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru,
	pekkas@netcore.fi, jmorris@namei.org, yoshfuji@linux-ipv6.org,
	kaber@trash.net
Subject: Re: [Patch 4/5] Network Drop Monitor: Adding drop monitor implementation & Netlink protocol
Date: Tue, 03 Mar 2009 14:14:50 -0800 (PST)	[thread overview]
Message-ID: <20090303.141450.98616272.davem@davemloft.net> (raw)
In-Reply-To: <20090303192107.GJ1480@hmsreliant.think-freely.org>

From: Neil Horman <nhorman@tuxdriver.com>
Date: Tue, 3 Mar 2009 14:21:07 -0500

> On Tue, Mar 03, 2009 at 09:19:09PM +0300, Evgeniy Polyakov wrote:
> > Hi Neil.
> > 
> > On Tue, Mar 03, 2009 at 12:04:35PM -0500, Neil Horman (nhorman@tuxdriver.com) wrote:
> > > +typedef enum {
> > > +	NET_DM_CFG_VERSION = 0,
> > > +	NET_DM_CFG_ALERT_COUNT,
> > > +	NET_DM_CFG_ALERT_DELAY,
> > > +	NET_DM_CFG_MAX,
> > > +} config_type_t;
> > > +
> > > +struct net_dm_config_entry {
> > > +	config_type_t type;
> > > +	uint64_t data;
> > > +};
> > > +
> > 
> > Ugh, please add either some comments about its alignment or some padding
> > fields.
> > 
> Yeah, I probably should align that to 64 bit boundaries for performance, thanks!

Actually you should use "aligned_u64" otherwise there will be
compat issues on 32-bit x86 on x86_64/ia64 since 32-bit x86
only 4-byte aligns 64-bit objects unless told otherwise.

And using anon-fixed type like an enum for "type" is also
likely not such a good idea.  I would just use a __u32
and some defines instead.

  reply	other threads:[~2009-03-03 22:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 17:04 [Patch 4/5] Network Drop Monitor: Adding drop monitor implementation & Netlink protocol Neil Horman
2009-03-03 18:19 ` Evgeniy Polyakov
2009-03-03 19:21   ` Neil Horman
2009-03-03 22:14     ` David Miller [this message]
2009-03-03 22:16     ` David Miller
2009-03-04 10:06       ` Patrick McHardy
2009-03-04 11:00         ` David Miller
2009-04-02  9:39           ` Herbert Xu
2009-04-02  9:50             ` David Miller
2009-04-02  9:52             ` David Miller
2009-04-02  9:59               ` Herbert Xu
2009-04-02 14:42                 ` Patrick McHardy
2009-04-02 14:45                   ` Herbert Xu
2009-04-02 14:57                     ` Patrick McHardy
2009-04-02 14:59                       ` Herbert Xu
2009-04-02 15:06                         ` Patrick McHardy
2009-04-02 15:09                           ` Herbert Xu
2009-04-02 15:14                             ` Patrick McHardy
2009-04-02 15:30                               ` Herbert Xu
2009-04-05  9:59                                 ` David Miller
2009-04-06 13:21                                   ` Patrick McHardy
2009-06-10  8:08                                     ` David Miller
2009-06-10 10:35                                       ` Patrick McHardy
2009-04-05  9:57                           ` David Miller
2009-04-05  9:56                     ` David Miller
2009-04-05  9:54                 ` David Miller
2009-03-04 11:44       ` Neil Horman
2009-03-05 19:27 ` Neil Horman
2009-03-11 16:17   ` David Miller
2009-03-11 19:51 ` Neil Horman
2009-03-13 19:10   ` 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=20090303.141450.98616272.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=pekkas@netcore.fi \
    --cc=yoshfuji@linux-ipv6.org \
    --cc=zbr@ioremap.net \
    /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).