From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: implement support for read-mostly sections
Date: Sun, 5 Dec 2010 23:04:34 +0000 [thread overview]
Message-ID: <20101205230434.GI9138@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTin5HiPRd=SF_kdvEnZjV7C3J+6MXKQL02zKKtp=@mail.gmail.com>
On Sun, Dec 05, 2010 at 10:18:27PM +0000, Catalin Marinas wrote:
> On 5 December 2010 11:43, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > diff --git a/arch/arm/kernel/vmlinux.lds.S b/arch/arm/kernel/vmlinux.lds.S
> > index cead889..1581f6d 100644
> > --- a/arch/arm/kernel/vmlinux.lds.S
> > +++ b/arch/arm/kernel/vmlinux.lds.S
> > @@ -167,6 +167,7 @@ SECTIONS
> >
> > NOSAVE_DATA
> > CACHELINE_ALIGNED_DATA(32)
> > + READ_MOSTLY_DATA(32)
>
> Should we change the alignments to 64?
When we have some way to tell vmlinux.lds.S what the cache line size is.
It should be a separate patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-05 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 11:42 [PATCH 0/2] Support for __read_mostly Russell King - ARM Linux
2010-12-05 11:43 ` [PATCH 1/2] ARM: implement support for read-mostly sections Russell King - ARM Linux
2010-12-05 22:18 ` Catalin Marinas
2010-12-05 23:04 ` Russell King - ARM Linux [this message]
2010-12-06 17:51 ` Catalin Marinas
2010-12-05 11:43 ` [PATCH 2/2] ARM: move high-usage mostly read variables in setup.c to __read_mostly Russell King - ARM Linux
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=20101205230434.GI9138@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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