netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH net-next] netem: use rb tree to implement the time queue
Date: Mon, 01 Jul 2013 18:08:04 -0700 (PDT)	[thread overview]
Message-ID: <20130701.180804.2068659449166342971.davem@davemloft.net> (raw)
In-Reply-To: <1372430457.3301.272.camel@edumazet-glaptop>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 28 Jun 2013 07:40:57 -0700

> From: Eric Dumazet <edumazet@google.com>
> 
> Following typical setup to implement a ~100 ms RTT and big
> amount of reorders has very poor performance because netem
> implements the time queue using a linked list.
> -----------------------------------------------------------
> ETH=eth0
> IFB=ifb0
> modprobe ifb
> ip link set dev $IFB up
> tc qdisc add dev $ETH ingress 2>/dev/null
> tc filter add dev $ETH parent ffff: \
>    protocol ip u32 match u32 0 0 flowid 1:1 action mirred egress \
>    redirect dev $IFB
> ethtool -K $ETH gro off tso off gso off
> tc qdisc add dev $IFB root netem delay 50ms 10ms limit 100000
> tc qd add dev $ETH root netem delay 50ms limit 100000
> ---------------------------------------------------------
> 
> Switch netem time queue to a rb tree, so this kind of setup can work at
> high speed.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Stephen Hemminger <stephen@networkplumber.org>

Looks good, nice work Eric, applied.

Let's see how long that skb->{prev,next} trick holds up ;-)

      reply	other threads:[~2013-07-02  1:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 14:40 [PATCH net-next] netem: use rb tree to implement the time queue Eric Dumazet
2013-07-02  1:08 ` David Miller [this message]

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=20130701.180804.2068659449166342971.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).