On 30-11-17, 15:57, Patrick Bellasi wrote: > Yes, that's a pretty trivial update with a confusing changelog. > > If we think it's worth to keep (and correct as well) I'll update the > commit message.
We also need to update the commit log based on feedback from Vikram on V2. Which said that the utilization can't change around the lock here as we are within rq lock section, though max can change (maybe). So this patch only takes care of locking before reading max. -- viresh
