• E
    net_sched: avoid too many hrtimer_start() calls · a9efad8b
    Eric Dumazet 提交于
    I found a serious performance bug in packet schedulers using hrtimers.
    
    sch_htb and sch_fq are definitely impacted by this problem.
    
    We constantly rearm high resolution timers if some packets are throttled
    in one (or more) class, and other packets are flying through qdisc on
    another (non throttled) class.
    
    hrtimer_start() does not have the mod_timer() trick of doing nothing if
    expires value does not change :
    
    	if (timer_pending(timer) &&
                timer->expires == expires)
                    return 1;
    
    This issue is particularly visible when multiple cpus can queue/dequeue
    packets on the same qdisc, as hrtimer code has to lock a remote base.
    
    I used following fix :
    
    1) Change htb to use qdisc_watchdog_schedule_ns() instead of open-coding
    it.
    
    2) Cache watchdog prior expiration. hrtimer might provide this, but I
    prefer to not rely on some hrtimer internal.
    Signed-off-by: NEric Dumazet <edumazet@google.com>
    Signed-off-by: NDavid S. Miller <davem@davemloft.net>
    a9efad8b
sch_api.c 45.5 KB