| To: | kaio@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Question about AIO behavior.... |
| From: | Christopher Smith <x@xxxxxxxx> |
| Date: | Sat, 07 Apr 2001 22:12:28 -0700 |
| In-reply-to: | <13200000.986604728@hellman> |
| Sender: | owner-kaio@xxxxxxxxxxx |
--On Friday, April 06, 2001 17:52:08 -0700 Christopher Smith <x@xxxxxxxx>
wrote:
Okay, I am seeing some behavior from KAIO which doesn't seem entirely right to me. If I do a read() on a socket which has no data, it blocks until there is some data available. However, if I do an aio_read() on the socket, it responds immediately, reading zero data, giving me that error code "29" I mentioned previously (aio_return() gives me 0, so it really thinks it didn't get any data). Okay, I've learned a bit more about what's going on now. It appears that the latest patch tries to do a seek if you do a read() on a socket (and presumably on a pipe as well). This results in a seek error (error 29). I'm going to look into patching this myself, but I thought I'd notify the group in the event that I was either wrong in my analysis or if someone had a fix (or got one done before I did). --Chris |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Finally got things right... ;-) (signals & threads in LInux), Christopher Smith |
|---|---|
| Next by Date: | Fix to make KAIO work with sockets (and likely pipes) again [was Re: Question about AIO behavior....], Christopher Smith |
| Previous by Thread: | Question about AIO behavior...., Christopher Smith |
| Next by Thread: | Fix to make KAIO work with sockets (and likely pipes) again [was Re: Question about AIO behavior....], Christopher Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |