From: Jonathan Morton <chromatix99@gmail.com>
To: Alessandro Bolletta <alessandro@mediaspot.net>
Cc: "Codel@lists.bufferbloat.net" <Codel@lists.bufferbloat.net>
Subject: Re: [Codel] Making tests on Tp-link router powered by Openwrt svn
Date: Thu, 20 Dec 2012 20:07:55 +0200 [thread overview]
Message-ID: <CAJq5cE1oiBQMF1i0-QV58c-4a2Kmdbkk=423x8bywbxDUuioQA@mail.gmail.com> (raw)
In-Reply-To: <d2kyh0lco6hoiio9wb5wc71v.1356025952977@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
Is the bottleneck actually at your router, or (as is more usual) at the
modem?
- Jonathan Morton
On Dec 20, 2012 7:57 PM, "Alessandro Bolletta" <alessandro@mediaspot.net>
wrote:
> Hi everybody,
> Today i made some tests on my tplink home router powered by the lastest
> snapshot build of Openwrt.
> So, i configured tc to make fq_codel the default queuing algorithm for 2
> eth ports available on the router (leaving unchanged default values).
> So, i started some TCP sessions through my Windows client and I loaded the
> available bandwidth...but the test wasn't going as expected because i
> experienced packet loss and high delays as i did when the default simple
> fifo queue was the default queue.
> Is there something that i'm not understanding?
>
> Thanks,
> Alessandro Bolletta
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
[-- Attachment #2: Type: text/html, Size: 1354 bytes --]
next prev parent reply other threads:[~2012-12-20 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 17:57 Alessandro Bolletta
2012-12-20 18:07 ` Jonathan Morton [this message]
2012-12-21 10:19 ` [Codel] R: " Alessandro Bolletta
2012-12-21 10:32 ` Dave Taht
2012-12-21 10:54 ` Dave Taht
2012-12-21 17:06 ` Kathleen Nichols
2012-12-21 17:13 ` Jim Gettys
2012-12-21 19:13 ` Kathleen Nichols
2012-12-21 19:34 ` Jim Gettys
2012-12-21 17:43 ` Dave Taht
2012-12-21 17:51 ` Kathleen Nichols
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='CAJq5cE1oiBQMF1i0-QV58c-4a2Kmdbkk=423x8bywbxDUuioQA@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=Codel@lists.bufferbloat.net \
--cc=alessandro@mediaspot.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