Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Better results from CeroWrt 3.10.28-16
Date: Mon, 3 Mar 2014 00:53:50 -0800	[thread overview]
Message-ID: <CAA93jw6=xU0tRKmK33L4wn3h8Tz+LBCjmbs5fh58HNqHpGBYEg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5vqBO02HiO_ysSFGLm7Tt8r0vnVAVm=PsBmNecu1mAeQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

On Mon, Mar 3, 2014 at 12:51 AM, Dave Taht <dave.taht@gmail.com> wrote:
> Wow. Mac TCP is certainly getting stuffed at 768KB up.
>
> using a wireshark filter of tcp.stream eq 18
>
> it looks like you are iw3, with 8 bytes of overhead on the wire, and
> although the MSS gets reduced slightly (not enough!)
> the window never gets below 132480. The throughput graph is reasonable
> regardless.... but I have to figure out a way to "see" if the RTO
> timer is firing or not. Thankfully there's an expert handy this
> afternoon.
>
> I'll setup a duplicate test here on a different OS and see what I see...
>
> supplying the rrul *json.gz files would let me do some totals plots....
>
> On Sun, Mar 2, 2014 at 6:28 PM, Rich Brown <richb.hanover@gmail.com> wrote:
>> Dave,
>>
>> I got the wireshark info. https://dl.dropboxusercontent.com/u/21403660/RRUL-Wireshark.zip
>>
>> It was my intent to replicate the RRUL -p all_scaled test with both 'auto' and '30ms' for the egress target. I hope I got it correct - both the settings and the wireshark capture.
>>
>> Rich
>>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html



-- 
Dave Täht

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

[-- Attachment #2: richthroughput.png --]
[-- Type: image/png, Size: 247543 bytes --]

  reply	other threads:[~2014-03-03  8:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 21:18 Rich Brown
2014-03-02 21:41 ` Dave Taht
2014-03-02 21:48   ` Sebastian Moeller
2014-03-03  1:38     ` Rich Brown
2014-03-05 18:52       ` Sebastian Moeller
2014-03-02 21:51   ` Aaron Wood
2014-03-02 22:19     ` Dave Taht
2014-03-03  1:27   ` Rich Brown
2014-03-03  1:41     ` Dave Taht
2014-03-03  1:43       ` Dave Taht
2014-03-03  1:49       ` Rich Brown
2014-03-03  2:00         ` Dave Taht
2014-03-03  2:28           ` Rich Brown
2014-03-03  8:51             ` Dave Taht
2014-03-03  8:53               ` Dave Taht [this message]
2014-03-03 13:35               ` Rich Brown
2014-03-03 13:43                 ` Toke Høiland-Jørgensen

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw6=xU0tRKmK33L4wn3h8Tz+LBCjmbs5fh58HNqHpGBYEg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    /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