Not sure what you meant here. The current code bases all its calculations of
intervals base on the begin time of slot zero. Even if slot zero is bad, it’s
total window is used in each time interval calculation. In the new code, a bad
slot is never used in any way even if it is slot zero.
> On Dec 6, 2016, at 01:43, Miroslav Lichvar <mlich...@redhat.com> wrote:
>> The change has a couple of things it does. First, it ignore bad slots. On
>> all the systems I’ve tested, slot one is always the worst slot, which long
>> delays, resulting in a baseline skew.
> The current code does that too.