linux-kernel - Re: linux cache routines for Write-back cache policy on MIPS24KE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0710011121300.20679@anakin>
Date:	Mon, 1 Oct 2007 11:23:05 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	veerasena reddy <veerasena_b@...oo.co.in>
cc:	linux-mips <linux-mips@...ux-mips.org>,
	"linux-kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux cache routines for Write-back cache policy on  MIPS24KE

On Mon, 1 Oct 2007, 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

It does both write back and invalidate.

> - 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.

Note that 2.6.18 is old. The above functions are intended to be removed.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/