Messages in this thread | | | Date | Tue, 15 Jun 1999 09:32:13 +0200 (CEST) | From | (Arjan van de Ven) | Subject | Re: Non-blocking read |
| |
In article <37659004.6C72667F@infolibria.com> you wrote: > Async. read-ahead would not be reliable, would it? The next time you > (as in your process that wants this data block) context switches in, the > read-ahead data may have disappeared from the buffer cache. Theres also > this added complication of second level indirection coming from the > inode.
When I (= the application) ask for a non-blocking read, I don't mind getting a -EAGAIN if the data is _not_ available right now. As long as it will be available sometime in the future, it is ok since I will ask again...
Greetings, Arjan van de Ven
- 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/
| |