diff options
| author | Eric Dumazet <edumazet@google.com> | 2018-09-28 19:28:44 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-10-02 08:18:51 +0200 |
| commit | fb420d5d91c1274d5966917725e71f27ed092a85 (patch) | |
| tree | f4a5a44cf2c8c53e9af214bc686c5a25736bca5e /net/sched/sch_mqprio.c | |
| parent | selftests/tls: Fix recv(MSG_PEEK) & splice() test cases (diff) | |
| download | linux-fb420d5d91c1274d5966917725e71f27ed092a85.tar.xz linux-fb420d5d91c1274d5966917725e71f27ed092a85.zip | |
tcp/fq: move back to CLOCK_MONOTONIC
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 want to converge later, we'll probably need to add
an skb field to differentiate the clock bases, or a socket option.
In the meantime, an UDP application will need to use CLOCK_MONOTONIC
base for its SCM_TXTIME timestamps if using fq packet scheduler.
Fixes: 72b0094f9182 ("tcp: switch tcp_clock_ns() to CLOCK_TAI base")
Fixes: 142537e41923 ("net_sched: sch_fq: switch to CLOCK_TAI")
Fixes: fd2bca2aa789 ("tcp: switch internal pacing timer to CLOCK_TAI")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: Leonard Crestez <leonard.crestez@nxp.com>
Tested-by: Leonard Crestez <leonard.crestez@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sched/sch_mqprio.c')
0 files changed, 0 insertions, 0 deletions