On Wed, May 29, 2002 at 11:03:20PM +0200, Kevin D. Kissell wrote: > While trampolines, breakpointing and JITing are the main > uses of user-mode cache manipulation (drivers are a whole > 'nother story), we really should have distinct capabilities for > I-stream modification and for explicit synchronizations of > the data storage hierarchy, for non-coherent multiprocessors > and user-manipulated DMA buffers. As to whether > those capabilities should be distinguished by system > call (sysmips vs. cacheflush) or by parameter to the > same system call, I don't have enough data to form > an opinion at this point. It should clearly be cacheflush(2); sysmips(2) is too coarse, too ugly interface. Another thing we'll still have to implement is the cachectl(2) syscall; for certain systems and applications fine control of the caching mode use for a memory mapping may result in major performance improvments. Ralf
