linux-mips
[Top] [All Lists]

Re: [SPAM] Cache aliasing issues using 4K pages.

To: The Engineer <lper.home@gmail.com>
Subject: Re: [SPAM] Cache aliasing issues using 4K pages.
From: Markus Gothe <markus.gothe@27m.se>
Date: Mon, 14 Jan 2008 23:34:10 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <1a18fe6d0801141225u2395ae6dj39d268014019b4a1@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1a18fe6d0801141225u2395ae6dj39d268014019b4a1@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
Lemme guess, it's not a dual-core as in SMP but a sub-CPU.
This usually involves that the memory differs, for example does it have a TLB. Which vendor and which core is it? I suppose you use some sort of firmware from the vendor to access the sub-CPU, right?

//Markus

On 14 Jan 2008, at 21:25, The Engineer wrote:

We are working with a 2.6.12 kernel on a dual-core mips architecture.
In this dual-core system, one core is running the linux kernel and the
other is used for some real-time handling (not directly controlled by
Linux)
We had different stability issues, which could be pinpointed to be
related with cache aliasing problems.
Cache aliasing happens when the same physical memory can be cached
twice as it is accessed by two different virtual addresses.
Indeed, for the index to select the correct cache line the virtual
address is used. If some bits of the virtual page address are used in
the cache index, aliasing can occur.


As there is no hardware solution in the mips to recover from this
(which would provide some cache coherency, even for one core), the
only intrinsic safe solution is to enlarge the page size, so that
cache indexing is only done by the offset address in the page (thus
the physical part of the address).
Another solution is to flush the cache if a page is being remapped to
an aliased address (but in our case linux does not has control on the
second core, which can cause issues with shared data between both
cores).
Currently the second solution is used in the kernel, but we found
different issues with it (for instance: we had to merge more recent
mips kernels, to get a reliable copy-on-write behaviour after
forks...).

Therefore some questions:
- Are there still some known issues with cache aliasing in the MIPS kernel?
- Are there known issues when using 16KB pages (8KB pages seems not be
possible due to tlb issues).

Thanks in advance,
Luc


_______________________________________

Mr Markus Gothe
Software Engineer

Phone: +46 (0)13 21 81 20 (ext. 1046)
Fax: +46 (0)13 21 21 15
Mobile: +46 (0)70 348 44 35
Diskettgatan 11, SE-583 35 Linköping, Sweden



Attachment: PGP.sig
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>