CACHE instruction on MIPS32 24KE

[Mohamed Bamakhrama]

Hi list,
I have one question regarding the CACHE instruction in the MIPS32
24KE core. In the software user's manual (page 317), it mentions that it is
possible to perform "fetch & lock" operation on a given cache line.
I am developing a driver for 2.4.31 kernel and I want to be able to
lock some "hot spots" inside the instruction cache to maximize the
throughput. Nevertheless, the manual states that if all the 4-ways of
the cache set were locked, then the core will just replace one of
them. So theoretically, the core should overwrite one of the ways in
case of the first collision and then use that overwritten line for
subsequent collisions. What I observe in my program is different. The
# of I$ misses is the same. I tried to move the locking code around
and when I did it just before the basic block I got an improvement of
20% only!!
My questions are:
1) Are there any parts in the kernel which unlocks the I$ lines under
some circumstances?
2) Is there anyone who worked with the cache instruction under MIPS
before and have any ideas about this behaviour?

Here is the macro used for cache locking:


***** BEGIN CODE *****

#define LOCK_IN_CACHE(function, lines)   \
      asm volatile (  ".set   mips32 \n"      \
                      ".set   noreorder \n"   \
                      "lock_me_" #function ": \n"      \
                      "       cache   0x1C, 0x00(%0) \n"      \
                      "       addiu   %z0, %z0, 0x20 \n"      \
                      "       sub     %z1, %z1, %z3  \n"      \
                      "       bgez    %z1, lock_me_" #function " \n"   \
                      ".set   mips0 \n"       \
                      : : "Jr" (&function),    \
                      "Jr" (lines), "Jr" (0), "Jr" (1));

***** END CODE *****

Best Regards,

--
Mohamed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/