net_sched: sch_fq: properly set sk->sk_pacing_status
If fq_classify() recycles a struct fq_flow because
a socket structure has been reallocated, we do not
set sk->sk_pacing_status immediately, but later if the
flow becomes detached.
This means that any flow requiring pacing (BBR, or SO_MAX_PACING_RATE)
might fallback to TCP internal pacing, which requires a per-socket
high resolution timer, and therefore more cpu cycles.
Fixes: 218af599fa63 ("tcp: internal implementation for pacing")
Signed-off-by: Eric Dumazet <firstname.lastname@example.org>
Cc: Soheil Hassas Yeganeh <email@example.com>
Cc: Neal Cardwell <firstname.lastname@example.org>
Acked-by: Soheil Hassas Yeganeh <email@example.com>
Signed-off-by: David S. Miller <firstname.lastname@example.org>
1 file changed