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:40:01 +0100 [thread overview]
Message-ID: <20070801144001.GA12840@linux-mips.org> (raw)
In-Reply-To: <40378e40708010713p3d866a9dva7d69132e61497d6@mail.gmail.com>
On Wed, Aug 01, 2007 at 04:13:05PM +0200, Mohamed Bamakhrama wrote:
> I agree with you that it fits more to real-time systems. My point was
> that such a functionality can be added to the list of available macros
> (i.e. Fetch, invalidate) so that when the developer (of an embedded
> system for example) needs it, he/she can use it directly.
>
> Is it possible to submit a patch which adds this functionality?
It takes more than a small patch to add a few cacheop definitions. Linux
generiously uses Index cacheops and so would also blow away wired cache
lines and that would need to be prevented. But to answer your question,
with these notes, yes.
Ralf
prev parent reply other threads:[~2007-08-01 14:40 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
2007-08-01 14:13 ` Mohamed Bamakhrama
2007-08-01 14:40 ` Ralf Baechle [this message]
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=20070801144001.GA12840@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