Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Noah Causin <n0manletter@gmail.com>,
	make-wifi-fast@lists.bufferbloat.net,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	Felix Fietkau <nbd@nbd.name>,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] wifi airtime fairness patches could use	eyeballs	and testing
Date: Wed, 10 Aug 2016 22:06:39 +0200	[thread overview]
Message-ID: <E8B9BE5E-CBDD-4F7D-8390-9A4415FEBA95@toke.dk> (raw)
In-Reply-To: <CAA93jw5_cbzrzG6VJ09pwBEX4TGB+EmvbFR=Ui=gXnVg=f2yNA@mail.gmail.com>



On 10 August 2016 21:35:40 CEST, Dave Taht <dave.taht@gmail.com> wrote:
>Wow, that *is* weird. It is good to see the tcp window changing on
>this set of data (it wasn't before), and CWRs, but... hmmm... SCIENCE.
>
>Enabling ecn on both sides will rule out some potential bugs.

Yeah, couldn't get ecn to work on the host I was using as the other endpoint on that test. Will try with another box that's not on quite as ancient a kernel.  Was also planning to disable codel (by setting a very high target) to try to narrow down the problem.

>Doubling the quantum again (3028) will go easier on the other side's
>tcp stack. (unless 3028 is the wrong number at this layer)

The endpoints have plenty of CPU.

>Are you thinking timestamps are being scribbled on?

Not necessarily; that was related to something else...

-Toke

  reply	other threads:[~2016-08-10 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 11:28 [Cerowrt-devel] " Dave Taht
2016-08-10 13:06 ` [Cerowrt-devel] [Make-wifi-fast] " Noah Causin
2016-08-10 13:11   ` Dave Taht
2016-08-10 15:04   ` Toke Høiland-Jørgensen
2016-08-10 19:35     ` Dave Taht
2016-08-10 20:06       ` Toke Høiland-Jørgensen [this message]
2016-08-10 21:50         ` Toke Høiland-Jørgensen
2016-08-10 21:58           ` Dave Taht
2016-08-10 22:05             ` Toke Høiland-Jørgensen
2016-08-10 22:07               ` Toke Høiland-Jørgensen
2016-08-10 22:18               ` Jonathan Morton
2016-08-10 22:45                 ` Toke Høiland-Jørgensen
2016-08-11  6:43                   ` Dave Taht
2016-08-11  9:16                     ` Toke Høiland-Jørgensen
2016-08-14 22:21   ` Dave Taht
2016-08-14 22:49     ` Aaron Wood
2016-08-14 23:02       ` Dave Taht
2016-08-14 23:04         ` Aaron Wood

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=E8B9BE5E-CBDD-4F7D-8390-9A4415FEBA95@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=n0manletter@gmail.com \
    --cc=nbd@nbd.name \
    --cc=sw@simonwunderlich.de \
    /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