From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] clocksource/drivers/tango-xtal: Replace code by clocksource_mmio_init
Date: Fri, 13 Nov 2015 10:26:42 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.11.1511131025140.3903@nanos> (raw)
In-Reply-To: <5645F616.9060707@sigmadesigns.com>
On Fri, 13 Nov 2015, Marc Gonzalez wrote:
> On 13/11/2015 15:16, Daniel Lezcano wrote:
> > For example:
> >
> > struct clockcommon {
> > u32 mult;
> > u32 shift;
> > int rating;
> > void __iomem *base;
> > char *name;
> > int irq;
> > };
> >
> > struct clocksource {
> > struct clockcommon common; /* MUST be the first field */
> > cycle_t (*read)(struct clocksource *cs);
> > cycle_t mask;
> > ...
> > };
>
> According to my notes, commit 369db4c952 grouped hot-path data
> into a single cache line (hence ____cacheline_aligned).
>
> (AFAIR, ARMv7 ARCH_MULTIPLATFORM assumes CACHE_LINE=64)
>
> Not sure how to make the two concepts (common base struct and
> grouping hot data) play nicely, without wasting a lot of space
> on padding.
It wont play well. We are not going to change the layout of struct
clocksource because it will hurt the sane use cases for no reason.
Thanks,
tglx
next prev parent reply other threads:[~2015-11-13 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:58 Daniel Lezcano
2015-11-13 12:20 ` Marc Gonzalez
2015-11-13 14:16 ` Daniel Lezcano
2015-11-13 14:39 ` Marc Gonzalez
2015-11-13 15:26 ` Thomas Gleixner [this message]
2015-11-13 15:39 ` Marc Gonzalez
2015-11-17 12:22 ` Daniel Lezcano
2015-11-17 12:48 ` Marc Gonzalez
2015-11-17 13:08 ` Måns Rullgård
2015-11-17 13:11 ` Daniel Lezcano
2015-11-13 13:33 ` Marc Gonzalez
2015-11-13 14:18 ` Daniel Lezcano
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=alpine.DEB.2.11.1511131025140.3903@nanos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
/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
all inboxes | Powered by JetHome®