lkml.org 
[lkml]   [1999]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Cache incoherencies (WAS: New resources - pls, explain :-( )
Date
From
>The only way I see to make the fist issue safe is to have the ring
>descriptor entries non cachable.

Yes. This is the better solution for performance as well. The flushing
routines are really only suitable for large blocks such as data buffers.

>Non-cache coherent archs should probably
>define a kmalloc flag to allocate non cachable space. (I still don't know
>what is the cleanest way to get non-cachable space. ioremap ?).

Ioremap won't necessarily work on physical RAM. You should probably define
vmalloc_uncached or some such.

p.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.111 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site