On Sat, May 29, 2010 at 10:23:15AM +0100, Guido Trotter wrote: > On Thu, May 27, 2010 at 4:22 PM, Guido Trotter <[email protected]> wrote: > > This builds up on the "Master core scalability design doc" detailing the > > critical situations in the job queue and proposing how to fix them. The > > bulleted point list at the beginning is changed to subparagraph, as the > > job queue part is quite longer and more detailed, then the remediation > > section is updated removing the generic "we'll fix it somehow" paragraph > > to propose a real solution. > > > > Signed-off-by: Guido Trotter <[email protected]> > > ping? :) Could anyone take a look at this, please?
I looked at it, just didn't send email :) It sounds sane, but as I said offline, I think this will be tricky to implement properly (lock interaction & such). So I would propose we don't commit to this solution 100%, but leave open the decision pending some working code. LGTM on the design doc. iustin
