Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Asynchronous File I/O on Linux



On May 19, 2010, at 4:18 PM, Bill Bogstad wrote:
> 
> If I understand correctly, you are suggesting that the kernel should
> automatically read data at the new offset after an lseek() in case
> it's followed by a read().   I can see how that is a good idea for

Something like that.  Given a program that needs to perform computations before reading data, spawn a thread that reads the required data blocks so that they are cached when the main thread does its read() calls.

--Rich P.








BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org