buffer index there. By then, most of you would probably veto the
patch anyway ;-)
haha, touche :)
I still think it'd be the right thing, though. We can let the patch
speak for itself :).
- z
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Zach Brown wrote on Tuesday, January 02, 2007 5:06 PM
> To: Chen, Kenneth W
> > Given the previous patch "aio: add per task aio wait event condition"
> > that we properly wake up event waiting process knowing that we have
> > enough events to reap, it's just plain waste of time to insert itself
>
Given the previous patch "aio: add per task aio wait event condition"
that we properly wake up event waiting process knowing that we have
enough events to reap, it's just plain waste of time to insert itself
into a wait queue, and then immediately remove itself from the wait
queue for *every*
Given the previous patch aio: add per task aio wait event condition
that we properly wake up event waiting process knowing that we have
enough events to reap, it's just plain waste of time to insert itself
into a wait queue, and then immediately remove itself from the wait
queue for *every* event
Zach Brown wrote on Tuesday, January 02, 2007 5:06 PM
To: Chen, Kenneth W
Given the previous patch aio: add per task aio wait event condition
that we properly wake up event waiting process knowing that we have
enough events to reap, it's just plain waste of time to insert itself
into a
buffer index there. By then, most of you would probably veto the
patch anyway ;-)
haha, touche :)
I still think it'd be the right thing, though. We can let the patch
speak for itself :).
- z
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
The read event loop in the blocking path is also inefficient. For every
event it reap (if not blocking), it does the following in a loop:
while (i < nr) {
prepare_to_wait_exclusive
aio_read_evt
finish_wait
...
}
Given the previous patch
The read event loop in the blocking path is also inefficient. For every
event it reap (if not blocking), it does the following in a loop:
while (i nr) {
prepare_to_wait_exclusive
aio_read_evt
finish_wait
...
}
Given the previous patch
8 matches
Mail list logo
