CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>, codel@lists.bufferbloat.net
Subject: Re: [Codel] GRO (generic receive offload) is not helpful with codel and fq_codel
Date: Wed, 21 Nov 2012 23:57:06 -0800	[thread overview]
Message-ID: <1353571026.2590.731.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw6X6-S++yyfGTPfezzLs4BNqSXZ3nRmAL3GrpQ3Q0-C1Q@mail.gmail.com>

On Thu, 2012-11-22 at 08:22 +0100, Dave Taht wrote:
> qdisc fq_codel 120: parent 1:12 limit 10240p flows 16000 quantum 500
> target 20.0ms interval 100.0ms
>  Sent 2213780 bytes 4843 pkt (dropped 48, overlimits 0 requeues 0)
>  backlog 12160b 8p requeues 0
>   maxpacket 14546 drop_overlimit 0 new_flow_count 1237 ecn_mark 0
>                      *******
>   new_flows_len 1 old_flows_len 2

Yes, GRO/TSO are not good for speeds below 10Mb.

In your case, you probably have one Gigabit ethernet (allowing GRO
packets being constructed), forwarding to the WAN at 750 kbits ... 

Definitely GRO should be turned off in this case.

A GSO packet of 64KB would take about 600ms to be transmitted !

Ideally, we should segment GSO packets at these low forwarding rates,
and keep GRO turned on for local traffic (not forwarded)




      reply	other threads:[~2012-11-22  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  7:22 Dave Taht
2012-11-22  7:57 ` Eric Dumazet [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

  List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1353571026.2590.731.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dwmw2@infradead.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