Daniel Phillips writes:
> The quesion is, how do you know you're streaming? Some files are
> read/written many times and some files are accessed randomly. I'm
> trying to avoid penalizing these admittedly rarer, but still
> important cases.
I wonder if we're trying to do the impossible: an algorithm that works
great for very different workloads, without hints from the process.
Shouldn't we encourage use of madvise(2) more? And if needed, add
O_DROPBEHIND and similar flags for open(2).
The application knows how it's going to use data/memory. It should
tell the kernel so the kernel can choose the best algorithm.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
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 : Fri Aug 31 2001 - 21:00:25 EST