Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-announce@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Cerowrt 3.3.8-10 is released
Date: Wed, 11 Jul 2012 18:56:35 +0200	[thread overview]
Message-ID: <CAMZR1YAfPGYC611GThiJbNjZgK4QDqZoVDT_Cd7CC9+aGM8xhw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5cAgdpJ0qWaN-NdfXvvFENjgUgsPRGN+q4EZJeza7b8A@mail.gmail.com>

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

Hi Dave,

Thanks for a good, lengthy update. I wish you pleasant time travelling.

One question on ECN though.

On Tue, Jul 10, 2012 at 3:43 AM, Dave Taht <dave.taht@gmail.com> wrote:

> - ECN dropping - after several high level conversations with many
> people smarter than me, I decided that dropping ECN packets at a
> certain point made sense. So did everyone else. The "certain point"
> remains puzzling to all, and
> rather than continue to waste time on it in cero I decided to play
> with models instead, and frankly, hope that someone else comes up with
> some sane way to combine ECN and codel sojourn time.

So if we're dropping ECN packets and not of trying to allow them through to
communicate congestion am I better of enabling ECN on clients on my network
or not?

Regards,
Maciej

[-- Attachment #2: Type: text/html, Size: 1178 bytes --]

  parent reply	other threads:[~2012-07-11 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  1:43 Dave Taht
2012-07-10 21:38 ` [Cerowrt-devel] [Bloat] " Jim Reisert AD1C
2012-07-11 16:56 ` Maciej Soltysiak [this message]
2012-07-12 20:45   ` [Cerowrt-devel] " Maciej Soltysiak
2012-07-12 20:55     ` Dave Taht
2012-07-12 21:51       ` Dave Taht
2012-07-13  0:43         ` Dave Taht

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=CAMZR1YAfPGYC611GThiJbNjZgK4QDqZoVDT_Cd7CC9+aGM8xhw@mail.gmail.com \
    --to=maciej@soltysiak.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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