On Sat, Aug 05, 2006, Henrik Nordstrom wrote: > Ideally delay pools would kick the I/O going again when the pool have > been filled up, and we could then get rid of the periodic repoll of > deferred connections relying almost exclusively on > storeDeferRead/storeResumeRead signaling to indicate when I/O should > take place. (not sure delay pools should be using these.. probably the > low level commDefer/ResumeFD like today, but maybe..)
I mostly had that working in my branch but I didn't get around to coding what delay pools would have needed. Steven's stuff was in use and I decided to just go with what he had rather than having two parallel branches. But my branch is there (tidyup_deferred_reads) if anyone wants to pull the code out and finally kill deferred reads for good. adrian
