From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: alexander.duyck@gmail.com, netdev@vger.kernel.org,
aduyck@mirantis.com, john.r.fastabend@intel.com,
jhs@mojatatu.com, brouer@redhat.com
Subject: Re: [PATCH net] net_sched: avoid too many hrtimer_start() calls
Date: Tue, 24 May 2016 14:49:39 -0700 (PDT) [thread overview]
Message-ID: <20160524.144939.1690436082295084190.davem@davemloft.net> (raw)
In-Reply-To: <1464038696.5939.29.camel@edumazet-glaptop3.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 23 May 2016 14:24:56 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> 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: Eric Dumazet <edumazet@google.com>
This looks fine, applied, thanks Eric.
next prev parent reply other threads:[~2016-05-24 21:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 17:08 [RFC] net: remove busylock Eric Dumazet
2016-05-19 18:03 ` Alexander Duyck
2016-05-19 18:41 ` Rick Jones
2016-05-19 18:56 ` Eric Dumazet
2016-05-19 19:35 ` Eric Dumazet
2016-05-19 20:39 ` Alexander Duyck
2016-05-20 4:49 ` John Fastabend
2016-05-20 4:56 ` Eric Dumazet
2016-05-20 7:29 ` Jesper Dangaard Brouer
2016-05-20 13:11 ` Eric Dumazet
2016-05-20 13:47 ` Eric Dumazet
2016-05-20 14:16 ` Eric Dumazet
2016-05-20 17:49 ` Jesper Dangaard Brouer
2016-05-20 21:32 ` Eric Dumazet
2016-05-23 9:50 ` Jesper Dangaard Brouer
2016-05-23 21:24 ` [PATCH net] net_sched: avoid too many hrtimer_start() calls Eric Dumazet
2016-05-24 21:49 ` David Miller [this message]
2016-05-24 13:50 ` [RFC] net: remove busylock David Laight
2016-05-24 14:37 ` Eric Dumazet
2016-05-20 16:01 ` John Fastabend
2016-05-19 18:12 ` David Miller
2016-05-19 18:44 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160524.144939.1690436082295084190.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).