> The other problem besides the inability to handle IO errors is that > mmap()+msync() is synchronous. You need to go async to keep > the pipelines full.
msync(addr, len, MS_ASYNC); doesn't do what you want? > Now if someone wants to implement an aio version of msync and > mlock, that might do the trick. At least for MMU systems. > Non MMU systems just can't play mmap type games. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
