linux-mips
[Top] [All Lists]

Re: cacheops.h & r4kcache.h

To: Mohamed Bamakhrama <bamakhrama@gmail.com>
Subject: Re: cacheops.h & r4kcache.h
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 1 Aug 2007 15:01:14 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <40378e40708010618r7a93e58br206e7c47e685a05e@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <40378e40708010618r7a93e58br206e7c47e685a05e@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.14 (2007-02-12)
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

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