> Look, the pagecache is already smart. New stuff will replace unusued
> old stuff. On VM pressure, the pagecache will be pruned. Streaming I/O
> is a fundamentally different problem in that the data is so large it
> _continually_ thrashes the pagecache. Such I/O is sequential and
> use-once. You end up with a permanent waste of memory (the cached
> I/O).
When a process opens a file with O_STREAMING, it tells the kernel
it will use the data only once, but it tells nothing about other
tasks. If that process reads something which is already cached,
then it must not drop it because someone other used it recently
and IMHO pagecache only should be allowed to drop it.
> Let's prove we have a solution to this problem before going after
> tangent ones.
If "solution" means "code", sorry, I can't help :(
Bye.
-
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/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:37 EST