On Sun, Dec 16, 2012 at 12:25:49AM +0000, Eric Wong wrote: > Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: > > On Sat, 15 Dec 2012 00:54:48 +0000 > > Eric Wong <normalperson@xxxxxxxx> wrote: > > > > > Applications streaming large files may want to reduce disk spinups and > > > I/O latency by performing large amounts of readahead up front > > > > How does it compare benchmark wise with a user thread or using the > > readahead() call ? > > Very well. > > My main concern is for the speed of the initial pread()/read() call > after open(). > > Setting EARLY_EXIT means my test program _exit()s immediately after the > first pread(). In my test program (below), I wait for the background > thread to become ready before open() so I would not take overhead from > pthread_create() into account. > > RA=1 uses a pthread + readahead() > Not setting RA uses fadvise (with my patch) And if you don't use fadvise/readahead at all? > # readahead + pthread. > $ EARLY_EXIT=1 RA=1 time ./first_read 1G > 0.00user 0.05system 0:01.37elapsed 3%CPU (0avgtext+0avgdata 600maxresident)k > 0inputs+0outputs (1major+187minor)pagefaults 0swaps > > # patched fadvise > $ EARLY_EXIT=1 time ./first_read 1G > 0.00user 0.00system 0:00.01elapsed 0%CPU (0avgtext+0avgdata 564maxresident)k > 0inputs+0outputs (1major+178minor)pagefaults 0swaps You're not timing how long the first pread() takes at all. You're timing the entire set of operations, including cloning a thread and for the readahead(2) call and messages to be passed back and forth through the eventfd interface to read the entire file. Why even bother with another thread for readahead()? It implements *exactly* the same operation as fadvise(WILL_NEED) (ie. force_page_cache_readahead), so should perform identically when called in exactly the same manner... But again, you are interesting in the latency of the first read of 16k from the file, but you are asking to readahead 1GB of data. Perhaps your shoul dbe asking for readahead of something more appropriate to what you care about - the first read.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>