slow io_submit
Jens suparna hello
I have managed to understand why io_submit is sometimes very slow. It is because the device is plugged once too many io's are being sent. I have conducted a simple test with nr_request to default value of 128 and and 256.
and it proved to be correct.
I would truely appreciate your comment on this.
Signature · 1 line
Raz
Quoted 7 lines · Raz Ben-Jehuda(caro)
Jens suparna hello
I have managed to understand why
io_submitis sometimes very slow. It is because the device is plugged once too many io's are being sent. I have conducted a simple test withnr_requestto default value of 128 and and 256.
and it proved to be correct.
I don't understand your email. The device is plugged when it is empty, not when it has emptied the request list.
Quoted 1 line
I would truely appreciate your comment on this.
On what? :-)
If it's no blocking and returning EAGAIN instead, then I agree this is what should eventually happen. Right now nobody is working on that afaik, so it's not something that will hit the next kernel.
Signature · 1 line
Jens Axboe
Quoted 11 lines · Jens Axboe
Quoted 7 lines · Raz Ben-Jehuda(caro)
Jens suparna hello
I have managed to understand why
io_submitis sometimes very slow. It is because the device is plugged once too many io's are being sent. I have conducted a simple test withnr_requestto default value of 128 and and 256.
and it proved to be correct.I don't understand your email. The device is plugged when it is empty, not when it has emptied the request list.
first , i am not top posting you.
I made a mistake and associated plugging with a full queue.
Quoted 6 lines
Quoted 1 line
I would truely appreciate your comment on this.
On what? :-)
If it's no blocking and returning EAGAIN instead, then I agree this is what should eventually happen.
Who returns EGAIN to whom ? I am not sure i understand what you mean here.
Quoted 2 lines
Right now nobody is working on that
afaik, so it's not something that will hit the next kernel.
thank you
raz
Quoted 4 lines
--
Jens Axboe
Signature · 1 line
Raz
Quoted 1 line · Raz Ben-Jehuda(caro)
Who returns EGAIN to whom ? I am not sure i understand what you mean here.
If the queue is full then io_sumbit() should return EAGAIN or some other error to indicate that the queue is full, but right now it just blocks instead.
Quoted 8 lines · Phillip Susi
Quoted 2 lines · Raz Ben-Jehuda(caro)
Who returns EGAIN to whom ? I am not sure i understand what you mean
here.If the queue is full then
io_sumbit()should return EAGAIN or some other error to indicate that the queue is full, but right now it just blocks instead.
thanks Phiilip
But... hmmm ... should'nt an asynchronous operation act as "send and forget" . isn't "queue full" a problem that aio must at least try and handle before returning to the user ?
Signature · 1 line
Raz
Quoted 4 lines · Raz Ben-Jehuda(caro)
thanks Phiilip
But... hmmm ... should'nt an asynchronous operation act as "send and forget" . isn't "queue full" a problem that aio must at least try and handle before returning to the user ?
It is handling it; by blocking until the queue is not full. A better way of handling it would be to return in such a way that the caller knows the queue is full and needs to wait before it can submit more requests, possibly doing some computation or submitting requests to other devices in the mean time.