From: Alessandro Bolletta <alessandro@mediaspot.net>
To: Jaume Barcelo <jaume.barcelo@upf.edu>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: [Codel] R: testbed for testing fq_codel on wifi doesn't work as expected
Date: Mon, 3 Jun 2013 08:35:35 +0000 [thread overview]
Message-ID: <F52F175DFC537F48A43937B50B44BCA27704AED5@EXCHANGE.mediaspot.local> (raw)
In-Reply-To: <CAJpd8ptGOYJGz+3kFi60JAZpRPjzFpD_vXm4OAf9PQw=COcfzg@mail.gmail.com>
Hi Jaume,
the dropping technique should involve every type of packet fulling the queue, including UDP packets.
It seems that there's something wrong with my configuration.
--
Alessandro Bolletta
Mediaspot S.r.l.
-----Messaggio originale-----
Da: Jaume Barcelo [mailto:jaume.barcelo@upf.edu]
Inviato: lunedì 3 giugno 2013 10.32
A: Alessandro Bolletta
Oggetto: Re: [Codel] testbed for testing fq_codel on wifi doesn't work as expected
Hi Alessandro,
I am a newbie here. I wanted to ask why do you use udp to saturate the link. I thought that codel was meant to throttle tcp flows.
Cheers,
Jaume
On Sat, Jun 1, 2013 at 1:09 PM, Alessandro Bolletta <alessandro@mediaspot.net> wrote:
> Hi everybody,
>
> I made a little testbed in my office with 2 Ubiquiti Nanobridge M5 and
> 2 TPlink 741nd.
>
> Nanobridges are simply connected in AP-STA mode and relaying traffic
> to the two TPLinks where i'm running batman-adv. So I bridged the bat0
> interface create by batman-adv with one of the ethernet ports offered
> by the ar71xx CPU. So I connected two laptops to the bridge at both
> ends and I pushed up a bidirectional UDP flow filling the wifi link
> available bandwidth (I saw that it constantly runs at 33Mbps in download and 37Mbps in upload).
>
> In every device (tplinks and ubnts) i'm running OpenWRT BARRIER
> BREAKER (Bleeding Edge, r36692), running on kernel 3.8.12
>
> I executed Dave Taht's debloat script for bash (and also the
> lua-compatible
> one) on every device, but if i try to make a ping starting from a
> laptop to the opposite laptop, these are the times that I get (sorry,
> it's written in italian. "Richiesta scaduta" means "expired reply"):
>
>
>
> Risposta da 192.168.2.25: byte=32 durata=259ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=281ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=285ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=91ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=130ms TTL=128
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=251ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=188ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=156ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=279ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=314ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=288ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=324ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=297ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=318ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=301ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=115ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=312ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=292ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=266ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=227ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=91ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=266ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=190ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=161ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=132ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=118ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=166ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=247ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=281ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=282ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=288ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=165ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=251ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=307ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=294ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=297ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=275ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=288ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=282ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=273ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=224ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=159ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=103ms TTL=128
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=186ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=225ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=299ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=112ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=171ms TTL=128
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=175ms TTL=128
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=147ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=211ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=279ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=279ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=228ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=219ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=167ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=177ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=197ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=265ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=275ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=237ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=237ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=285ms TTL=128
>
> Richiesta scaduta.
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=166ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=262ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=275ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=30ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=84ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=249ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=244ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=201ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=110ms TTL=128
>
> Richiesta scaduta.
>
> Risposta da 192.168.2.25: byte=32 durata=220ms TTL=128
>
> Risposta da 192.168.2.25: byte=32 durata=240ms TTL=128
>
>
>
>
>
> While if I ping while i'm not doing traffic at all I get 1ms RTT
> replies without packet loss.
>
> Can you help me to find the cause of this bufferbloat?
>
>
>
> Thanks
>
> Alessandro
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
next prev parent reply other threads:[~2013-06-03 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 11:09 [Codel] " Alessandro Bolletta
[not found] ` <CAJpd8ptGOYJGz+3kFi60JAZpRPjzFpD_vXm4OAf9PQw=COcfzg@mail.gmail.com>
2013-06-03 8:35 ` Alessandro Bolletta [this message]
[not found] ` <CAJpd8puSZELTrLVbTe_9G3FmxLD3JQc0hP0=wf=0m3QQZzkeQw@mail.gmail.com>
2013-06-03 8:57 ` [Codel] R: " Alessandro Bolletta
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=F52F175DFC537F48A43937B50B44BCA27704AED5@EXCHANGE.mediaspot.local \
--to=alessandro@mediaspot.net \
--cc=codel@lists.bufferbloat.net \
--cc=jaume.barcelo@upf.edu \
/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