From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: force dst_default_metrics to const section
Date: Wed, 08 Aug 2012 00:34:14 +0200 [thread overview]
Message-ID: <1344378854.28967.201.camel@edumazet-glaptop> (raw)
In-Reply-To: <1344377561.2688.66.camel@bwh-desktop.uk.solarflarecom.com>
On Tue, 2012-08-07 at 23:12 +0100, Ben Hutchings wrote:
> On Tue, 2012-08-07 at 22:55 +0200, Eric Dumazet wrote:
> > From: Eric Dumazet <edumazet@google.com>
> >
> >
> > > Some day the compiler may be smart enough to ignore the different
> > > between explicit and implicit zero-initialisation, and put it back in
> > > BSS. Declaring this __cache_aligned_in_smp might be a better option.
> >
> > __cache_aligned_in_smp aligns start of the structure, but can be
> > followed by another var in same cache line. Yes, this is bad.
>
> Oh, that's unexpected.
>
> > By the way we dont care of cache alignment on this structure, only it
> > should be const. Its a soft requirement, machine wont crash if it is not
> > the case.
>
> Right.
>
> > If compiler is smart one day as you say (it should first be non buggy
> > IMHO), then we can add a non zero field like this :
> [...]
>
> That would work, but it's ugly! How about defining and using a
> meaningfully-named macro that expands to __section(.rodata)?
You are kidding. I prefer plain C and not having to mess with all
arches.
next prev parent reply other threads:[~2012-08-07 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 16:11 [PATCH] net: force dst_default_metrics to const section Eric Dumazet
2012-08-07 20:15 ` Ben Hutchings
2012-08-07 20:55 ` Eric Dumazet
2012-08-07 22:12 ` Ben Hutchings
2012-08-07 22:34 ` Eric Dumazet [this message]
2012-08-07 22:44 ` Ben Hutchings
2012-08-07 22:56 ` Eric Dumazet
2012-08-07 23:17 ` David Miller
2012-08-08 23:00 ` David Miller
2012-08-07 21:55 ` David Miller
2012-08-07 22:09 ` Eric Dumazet
2012-08-07 22:11 ` Eric Dumazet
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=1344378854.28967.201.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--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