From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Siarhei Siamashka <siarhei.siamashka@nokia.com>
Cc: ext Jamie Lokier <jamie@shareable.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: copy_page.S: take into account the size of the cache line
Date: Wed, 15 Jul 2009 14:55:53 +0100 [thread overview]
Message-ID: <20090715135553.GB15533@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <200907151612.20240.siarhei.siamashka@nokia.com>
On Wed, Jul 15, 2009 at 04:12:19PM +0300, Siarhei Siamashka wrote:
> On Saturday 11 July 2009 02:51:23 ext Jamie Lokier wrote:
> > Kirill A. Shutemov wrote:
> > > From: Kirill A. Shutemov <kirill@shutemov.name>
> > >
> > > Optimized version of copy_page() was written with assumption that cache
> > > line size is 32 bytes. On Cortex-A8 cache line size is 64 bytes.
> > >
> > > This patch tries to generalize copy_page() to work with any cache line
> > > size if cache line size is multiple of 16 and page size is multiple of
> > > two cache line size.
> > >
> > > Unfortunately, kernel doesn't provide a macros with correct cache size.
> > > L1_CACHE_SHIFT is 5 on any ARM. So we have to define macros for this
> > > propose by ourself.
> >
> > Why don't you fix L1_CACHE_SHIFT for Cortex-A8?
>
> That's the plan.
L1_CACHE_SHIFT is supposed to be a constant and the maximum cache line
shift for the processors in use.
Other functions (eg, dma_get_cache_alignment) can return either this or
the real cache line size.
next prev parent reply other threads:[~2009-07-15 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 16:23 Kirill A. Shutemov
2009-07-10 23:51 ` Jamie Lokier
2009-07-15 13:12 ` Siarhei Siamashka
2009-07-15 13:55 ` Russell King - ARM Linux [this message]
2009-09-02 13:24 [PATCH 2/2] " Russell King - ARM Linux
2009-09-02 17:19 ` [PATCH] " Kirill A. Shutemov
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=20090715135553.GB15533@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=jamie@shareable.org \
--cc=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=siarhei.siamashka@nokia.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®