[lkml]   [2001]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [resent PATCH] Re: very slow parallel read performance
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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:58    [W:1.749 / U:0.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site