From: veerasena reddy <veerasena_b@yahoo.co.in>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips <linux-mips@linux-mips.org>,
"linux-kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux cache routines for Write-back cache policy on MIPS24KE
Date: Mon, 1 Oct 2007 13:10:59 +0100 (BST) [thread overview]
Message-ID: <535696.48077.qm@web8403.mail.in.yahoo.com> (raw)
In-Reply-To: <20071001105954.GB23647@linux-mips.org>
Hi Ralf,
Thanks for the reply.
Is there any problem if we use the below API's in
linxu-2.6.18
- dma_cache_wback_inv()
- dma_cache_wback()
- dma_cache_inv()
functionality wise, especially in r4k.c i dont see any
difference between the implementation of these APIs.
Can we apply the 2.6.24 patch to kill these APIs on
2.6.18 kernel? In this case what APIs i can use for
writeback, invalidation or both?
I couldn't find any info. related to the above API in
DMA-API.txt. Could you please give some pointers on
the usage/working of these APIs.
Regards,
Veerasena.
--- Ralf Baechle <ralf@linux-mips.org> wrote:
> On Mon, Oct 01, 2007 at 10:04:32AM +0100, veerasena
> reddy wrote:
>
> > I have ported Linux-2.6.18 kernel on MIPS24KE
> > processor. I am using write back cache policy.
> >
> > Could you please guide me under what cases the
> below
> > cache API's are being used:
> > - dma_cache_wback_inv() : Could you explain what
> > exactly this function does
> > - dma_cache_wback() : This function write back the
> > cache data to memory
> > - dma_cache_inv : This function invalidate the
> cache
> > tags. so subsequent access will fetch from memory.
> >
> > Once I looked the above function definitions in
> > linux-2.6.18/arch/mips/mm/c-r4k.c.
> > All these function's implemetation are same except
> > bc_wbak_inv() is called in both
> dma_cache_wback-inv()
> > and dma_cache_wback(), where as bc_inv() is called
> in
> > case of dma_cache_inv.
> >
> > Also, bc_inv()/bc_wbak_inv are define as null
> > implementation for R4000.
> > That means all three functions are doing same
> > functionality in case of R4000.
> >
> > What are the difference between these three
> functions.
> > Under what cases these functions are used.
>
> An internal only interface to be used with I/O cache
> coherency.
>
> > Please guide me if you have any links which will
> > explain these API's.
>
> Easy answer, don't use them, for 2.6.24 I've queued
> a patch to kill this
> API. Documentation/DMA-API.txt documents how to
> properly deal with I/O
> coherency in Linux.
>
> Ralf
>
Save all your chat conversations. Find them online at http://in.messenger.yahoo.com/webmessengerpromo.php
next prev parent reply other threads:[~2007-10-01 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 9:04 linux cache routines for Write-back cache policy on MIPS24KE veerasena reddy
2007-10-01 9:23 ` Geert Uytterhoeven
2007-10-01 10:51 ` veerasena reddy
2007-10-01 11:42 ` Geert Uytterhoeven
2007-10-01 12:13 ` veerasena reddy
2007-10-01 10:59 ` Ralf Baechle
2007-10-01 12:10 ` veerasena reddy [this message]
2007-10-03 10:57 ` Ralf Baechle
2007-10-08 13:58 ` veerasena reddy
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=535696.48077.qm@web8403.mail.in.yahoo.com \
--to=veerasena_b@yahoo.co.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.