This, I think, is definitely the right kind of approach to take.
I do not believe in raw IO - even for streaming audio it's just too common
for the data to have been available in the cache, and by using raw IO you
(for absolutely no good reason) just made the machine do more IO than it
should have.
There are very specific cases where the application knows that its dataset
is larger than physical memory, but those tend to be limited to quite
large problems. And they're getting larger.
But having a better way to decide what to throw out - that I am a strong
believer in.
Linus "raw IO - just say no" Torvalds
-
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/