From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Fix 32bit kernels on R4k with 128 byte cache line size
Date: Tue, 8 Jul 2008 14:02:34 +0100 [thread overview]
Message-ID: <20080708130234.GA29470@linux-mips.org> (raw)
In-Reply-To: <20080708124634.4EDFBC3562@solo.franken.de>
On Tue, Jul 08, 2008 at 02:46:34PM +0200, Thomas Bogendoerfer wrote:
> The generated copy_page for R4k CPU with a 128 byte cache line size used
> Create Dirty Exclusive cache line operations even if only part of the
> cache line was filled. This change avoids generating cache operations,
> if only part of the cache line size is copied in one loop. It also
> increases the maxmimum loop size, because the generated code even fits
> into the available space for r4k CPUs with 128 byte cache line size.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Thanks - another important fix in the last minute ...
Applied, will send to Linus tonight.
Ralf
prev parent reply other threads:[~2008-07-08 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 12:46 [PATCH] Fix 32bit kernels on R4k with 128 byte cache line size Thomas Bogendoerfer
2008-07-08 13:02 ` Ralf Baechle [this message]
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=20080708130234.GA29470@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.