From: "Kim, Jong-Sung" <jsungkim@lge.com>
To: <linux-mips@linux-mips.org>
Subject: Reading an entire cacheline
Date: Tue, 18 Apr 2006 09:37:18 +0900 [thread overview]
Message-ID: <058801c66280$3fa1ebb0$f3479696@LGE.NET> (raw)
Hi,
Is there any way to read an entire cacheline from the MIPS5Kf? Four
sequential cache instructions do similarly, but sometimes the tags from a
same cacheline differ. How can I read a consistent cacheline safely?
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: "Kim, Jong-Sung" <jsungkim@lge.com>
To: linux-mips@linux-mips.org
Subject: Reading an entire cacheline
Date: Tue, 18 Apr 2006 09:37:18 +0900 [thread overview]
Message-ID: <058801c66280$3fa1ebb0$f3479696@LGE.NET> (raw)
Message-ID: <20060418003718.L62s0I9RU8XjXFKdx9fYW6ujeDA4MgHC0NbHGg6_i3c@z> (raw)
Hi,
Is there any way to read an entire cacheline from the MIPS5Kf? Four
sequential cache instructions do similarly, but sometimes the tags from a
same cacheline differ. How can I read a consistent cacheline safely?
Thanks.
next reply other threads:[~2006-04-18 0:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 0:37 Kim, Jong-Sung [this message]
2006-04-18 0:37 ` Reading an entire cacheline Kim, Jong-Sung
2006-04-24 7:23 ` Kim, Jong-Sung
2006-04-24 7:23 ` Kim, Jong-Sung
2006-04-24 7:40 ` Kevin D. Kissell
2006-04-24 7:40 ` Kevin D. Kissell
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 9:52 Kim, Jong-Sung
2006-04-24 9:52 ` Kim, Jong-Sung
2006-04-26 8:47 ` Kim, Jong-Sung
2006-04-26 8:47 ` Kim, Jong-Sung
2006-04-26 9:48 ` Kevin D. Kissell
2006-04-26 9:48 ` Kevin D. Kissell
2006-04-26 10:16 ` Thiemo Seufer
2006-04-26 11:24 ` Kevin D. Kissell
2006-04-26 11:24 ` Kevin D. Kissell
2006-04-27 5:04 ` Kim, Jong-Sung
2006-04-27 5:04 ` Kim, Jong-Sung
2006-04-27 5:13 ` Kim, Jong-Sung
2006-04-27 5:13 ` Kim, Jong-Sung
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='058801c66280$3fa1ebb0$f3479696@LGE.NET' \
--to=jsungkim@lge.com \
--cc=linux-mips@linux-mips.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