Messages in this thread | | | From | "Albert D. Cahalan" <> | Subject | Re: Missing cache flush. | Date | Wed, 6 Jun 2001 04:32:27 -0400 (EDT) |
| |
David S. Miller writes: > David Woodhouse writes:
>>> Call it flush_ecache_full() or something. >> >> Strange name. Why? How about __flush_cache_range()? > > How about flush_cache_range_force() instead? > > I want something in the name that tells the reader "this flushes > the caches, even though under every other ordinary circumstance > you would not need to".
"flush" means what to you?
write-back write-back-and-invalidate discard-and-invalidate
All 3 behaviors are useful to me, and a few more. I've been using chunks of PowerPC assembly. Using PowerPC mnemonics...
dcba -- allocate a cache block with undefined content dcbf -- write to RAM, then invalidate ("data cache block flush") dcbi -- invalidate, discarding any data dcbst -- initiate write if dirty dcbt -- prefetch, hinting about future load instructions dcbtst -- prefetch, hinting about future store instructions dcbz -- allocate and zero a cache block (cacheable mem only!)
So dcbf_range() and dcbi_range() sound good to me. :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |