From: Ben Hutchings <bhutchings@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net_sched: add 64bit rate estimators
Date: Wed, 5 Jun 2013 21:06:09 +0100 [thread overview]
Message-ID: <1370462769.1918.7.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <1370461057.24311.296.camel@edumazet-glaptop>
On Wed, 2013-06-05 at 12:37 -0700, Eric Dumazet wrote:
> On Wed, 2013-06-05 at 19:55 +0100, Ben Hutchings wrote:
> > On Tue, 2013-06-04 at 22:00 -0700, Eric Dumazet wrote:
> > > From: Eric Dumazet <edumazet@google.com>
> > >
> > > struct gnet_stats_rate_est contains u32 fields, so the byte per second
> > > field can wrap at 34360Mbit.
> > >
> > > Add a new gnet_stats_rate_est64 structure to get 64bit bps field, and
> > > switch the kernel to use this structure natively.
> > [...]
> > > /**
> > > + * struct gnet_stats_rate_est64 - rate estimator
> > > + * @bps: current byte rate
> > > + * @pps: current packet rate
> > > + */
> > > +struct gnet_stats_rate_est64 {
> > > + __u64 bps;
> > > + __u32 pps;
> > > +} __attribute__ ((packed));
> > [...]
> >
> > Using attribute packed (which should be written as __packed) forces the
> > alignment of each member and the structure as a whole to be 1. For an
> > architecture where unaligned access is expensive, gcc will make all
> > reads and writes use byte operations.
> >
> > I think you have to add a dummy __u32 member instead.
>
> Its exported to userland so __packed is not available. Or has this been
> changed lately ?
Sorry, you're quite right.
> This structure is only used in very slow path, in the rate estimator
> thing, so the unaligned accesses are not a problem at all.
>
> I made this choice to not increase sizeof(struct Qdisc) and the
> alignments as well.
>
> If you think there is an issue with userland, we could use a
> gnet_stats_rate_est64_packed in kernel, and a gnet_stats_rate_est64 in
> userland.
If you're sure this is the right trade-off then I accept that. I
thought you were using packed to ensure the structure layout was
consistent between userland and kernel, and might not have realised the
unfortunate effect on alignment.
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.
next prev parent reply other threads:[~2013-06-05 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 5:00 [PATCH net-next] net_sched: add 64bit rate estimators Eric Dumazet
2013-06-05 18:55 ` Ben Hutchings
2013-06-05 19:37 ` Eric Dumazet
2013-06-05 20:06 ` Ben Hutchings [this message]
2013-06-05 23:07 ` Eric Dumazet
2013-06-06 8:39 ` David Laight
2013-06-06 15:43 ` [PATCH v2 " Eric Dumazet
2013-06-11 9:51 ` 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=1370462769.1918.7.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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