General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Taxonomy of various sender-side TCPs
Date: Fri, 11 Mar 2011 11:05:18 -0700	[thread overview]
Message-ID: <878vwlr0rl.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <20110311092157.23dea5e8@nehalam> (Stephen Hemminger's message of "Fri, 11 Mar 2011 09:21:57 -0800")

Stephen Hemminger <shemminger@vyatta.com> writes:

> On Fri, 11 Mar 2011 09:24:33 +0200
> Jonathan Morton <chromatix99@gmail.com> wrote:
>> Currently, CUBIC is the default TCP send-side algorithm in Linux.  It
>> seems likely that it will react correctly to ECN marking, but that a
>> higher rate of marking may be needed to bring it down to a given
>> buffering level.  From what I've read, SFB should be able to probe
>> for the correct marking rate on a per-flow basis, which is nice.
>> 
>> On the subject of ECN, my impression is that YouTube currently
>> doesn't enable it, but a one-man company I recently downloaded some
>> stuff from does.  I wonder if there's any reliable data on how many
>> of the most popular sites enable ECN if you ask for it.  Personally,
>> I think IPv6 and ECN should probably go together - v6 gear is new or
>> upgraded anyway so there shouldn't be any legacy problems.

I agree, but lack data. What TCP algorithms are available in the IPv6
stack on Linux? I know SFB works with both ipv4 and ipv6...

ECN has been enabled on kernel org for 8+ years.

>
> Even TCP window scaling is problematic. Many consumer bits of gear are seriously
> broken. I have had to turn off WS on my laptop to deal with hotel and conference
> wireless front ends.

Good tip.

-- 
Dave Taht
http://nex-6.taht.net

  parent reply	other threads:[~2011-03-11 18:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11  7:24 Jonathan Morton
2011-03-11 17:21 ` Stephen Hemminger
2011-03-11 17:57   ` Dave Täht
2011-03-11 18:07     ` Jonathan Morton
2011-03-11 18:12       ` Dave Täht
2011-03-11 18:25         ` Erica Han
2011-03-11 19:10       ` Dave Hart
2011-03-11 19:25         ` Jonathan Morton
2011-03-11 20:34           ` Erica Han
2011-03-11 20:46             ` Jonathan Morton
2011-03-11 22:20               ` Stephen Hemminger
2011-03-12  0:13                 ` Jonathan Morton
2011-03-12  0:18                   ` Stephen Hemminger
2011-03-11 18:00   ` Jonathan Morton
2011-03-11 18:10     ` Dave Täht
2011-03-11 18:05   ` Dave Täht [this message]
2011-03-11 18:21     ` Jonathan Morton
2011-03-11 18:31       ` Dave Täht
     [not found] ` <2231D7DC-D58A-41F8-8A06-05FF4EEA0EA5@nokia.com>
2011-03-14 13:55   ` [Bloat] FW: [Iccrg] Fwd: " Narasimha Reddy
2011-03-23 16:20 ` [Bloat] " Daniel Baluta

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

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

  git send-email \
    --in-reply-to=878vwlr0rl.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=shemminger@vyatta.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