CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Alessandro Bolletta <alessandro@mediaspot.net>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] R: Jumbo frames with fq_codel
Date: Mon, 25 Nov 2013 10:32:03 -0800	[thread overview]
Message-ID: <CAA93jw5OfX54DNqMyVgLGBWNEeZ-8jjef62bOMtGMNOD=60n+g@mail.gmail.com> (raw)
In-Reply-To: <F52F175DFC537F48A43937B50B44BCA27A71EA50@EXCHANGE.mediaspot.local>

On Mon, Nov 25, 2013 at 10:17 AM, Alessandro Bolletta
<alessandro@mediaspot.net> wrote:
>>On Mon, Nov 25, 2013 at 10:02 AM, Alessandro Bolletta <alessandro@mediaspot.net> wrote:
>> Hi guys,
>> I'm working on an environment which runs on jumbo ethernet frames (about 1550bytes) and I would ask you if do you think that it's needed >a trick in order to correctly debloat interfaces as ath9k and ag71xx which carries such big frames.
>
>>I am under the impression that the ag71xx does not support jumbo frames.
>>Slightly larger than usual frames? dunno.
>
> We are thinking to implement jumbo frames support on some devices based on ag71xx :)
> Many SoCs support up to 2028 bytes or 4076 bytes of MTU but the driver still can't manage MTUs higher than 1518bytes.
>
>>the ath9k supports frames up to the size of the wireless standards (23xx bytes or so)
>
> Yes.
>
>>fq_codel's internal quantum is the actual ip packet size, not the wire size.
>>at lower bandwidths it pays to have a lower quantum (like 300) on outgoing interfaces.
>
>>In openwrt the default on all interfaces is 300, which I dont necessarily agree with.
>
> Ok. I thought that codel would leverage on layer-2 parameters, as the size of the ethernet frame.

One of the beauties of codel is it doesn't care the size of the frame
at all, it only cares about how long it takes to deliver it.

Now, there are some interesting interactions between codel delivering
a big fat TSO string of packets and then a smaller packet (collatoral
damage), but they aren't bad, and there's fixes in 3.12 for tso that
make life saner.

fq_codel's quantum controls the degree of mixing between flows, set it
really low (say 300) to help voip and acks out on slow asymmetric
links, don't set it lower, otherwise leave it alone.

>>
>> Thanks
>>
>> --
>> Alessandro Bolletta
>> Mediaspot S.r.l.
>>
>>
>> _______________________________________________
>> Codel mailing list
>> Codel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/codel
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      parent reply	other threads:[~2013-11-25 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 18:02 [Codel] " Alessandro Bolletta
2013-11-25 18:04 ` Jonathan Morton
2013-11-25 18:09   ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:08 ` [Codel] " Dave Taht
2013-11-25 18:17   ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:26     ` Dave Taht
2013-11-25 18:30       ` [Codel] R: " Alessandro Bolletta
2013-11-25 18:32     ` Dave Taht [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='CAA93jw5OfX54DNqMyVgLGBWNEeZ-8jjef62bOMtGMNOD=60n+g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=alessandro@mediaspot.net \
    --cc=codel@lists.bufferbloat.net \
    /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