[PATCH net-next] tcp/fq: move back to CLOCK_MONOTONIC

2018-09-28 Thread Eric Dumazet
In the recent TCP/EDT patch series, I switched TCP and sch_fq clocks from MONOTONIC to TAI, in order to meet the choice done earlier for sch_etf packet scheduler. But sure enough, this broke some setups were the TAI clock jumps forward (by almost 50 year...), as reported by Leonard Crestez. If we

Re: [PATCH net-next] tcp/fq: move back to CLOCK_MONOTONIC

2018-09-28 Thread Leonard Crestez
On Fri, 2018-09-28 at 10:28 -0700, Eric Dumazet wrote: > In the recent TCP/EDT patch series, I switched TCP and sch_fq > clocks from MONOTONIC to TAI, in order to meet the choice done > earlier for sch_etf packet scheduler. > > But sure enough, this broke some setups were the TAI clock > jumps for

Re: [PATCH net-next] tcp/fq: move back to CLOCK_MONOTONIC

2018-09-28 Thread Eric Dumazet
On 09/28/2018 02:27 PM, Leonard Crestez wrote: > On Fri, 2018-09-28 at 10:28 -0700, Eric Dumazet wrote: >> In the recent TCP/EDT patch series, I switched TCP and sch_fq >> clocks from MONOTONIC to TAI, in order to meet the choice done >> earlier for sch_etf packet scheduler. >> >> But sure enoug

Re: [PATCH net-next] tcp/fq: move back to CLOCK_MONOTONIC

2018-10-01 Thread David Miller
From: Eric Dumazet Date: Fri, 28 Sep 2018 10:28:44 -0700 > In the recent TCP/EDT patch series, I switched TCP and sch_fq > clocks from MONOTONIC to TAI, in order to meet the choice done > earlier for sch_etf packet scheduler. > > But sure enough, this broke some setups were the TAI clock > jumps