> I found alternative approaches and did away with most of them. What I had > done is replaced the REPORTING_REQUESTED and reference count logic with > the state in order to guarantee that we will make our way through the list > and rearm the reporting thread if the work isn't completed. > > One thing I still think I need to split out based on Mel's comments is the > list rotation and probably the new budget value I added. Yeah, both probably make sense. > > As far as performance this new patch set performs better than the old one > did. Most of that is due to the fact that I increased the delay between > passes and dropped any optimizations for the shuffling code. That's interesting - and good :) I probably won't have enough time to look into #4 before Christmas - so I might wait for your resend and review after Christmas. -- Thanks, David / dhildenb
