From: "Mohamed Bamakhrama" <bamakhrama@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: CACHE instruction on MIPS32 24KE
Date: Fri, 13 Jul 2007 11:58:47 +0200 [thread overview]
Message-ID: <40378e40707130258j7e3571e2h8a97c332e0b1b4b6@mail.gmail.com> (raw)
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
reply other threads:[~2007-07-13 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40378e40707130258j7e3571e2h8a97c332e0b1b4b6@mail.gmail.com \
--to=bamakhrama@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®