From: Ralf Baechle <ralf@linux-mips.org>
To: Mohamed Bamakhrama <bamakhrama@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: cacheops.h & r4kcache.h
Date: Wed, 1 Aug 2007 15:01:14 +0100 [thread overview]
Message-ID: <20070801140114.GA23858@linux-mips.org> (raw)
In-Reply-To: <40378e40708010618r7a93e58br206e7c47e685a05e@mail.gmail.com>
On Wed, Aug 01, 2007 at 03:18:00PM +0200, Mohamed Bamakhrama wrote:
> In those two header files, flush & invalidate operations were
> implemented. Nevertheless, the MIPS32 core supports cache locking as
> well. Is there any implementations for Fetch&Lock instructions within
> the kernel?
No. The primary use for cache locking seems to be the rather extreme
realtime requirements, a league where Linux isn't playing quite yet.
For a more general purpose OS locking has a good chance of doing more
harm than help.
Ralf
next prev parent reply other threads:[~2007-08-01 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 13:18 cacheops.h & r4kcache.h Mohamed Bamakhrama
2007-08-01 14:01 ` Ralf Baechle [this message]
2007-08-01 14:13 ` Mohamed Bamakhrama
2007-08-01 14:40 ` Ralf Baechle
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=20070801140114.GA23858@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bamakhrama@gmail.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