General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I feel an urge to update this
Date: Thu, 25 Sep 2014 10:49:47 -0700	[thread overview]
Message-ID: <542455BB.70608@hp.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409251924340.14735@uplift.swm.pp.se>

On 09/25/2014 10:26 AM, Mikael Abrahamsson wrote:
> On Thu, 25 Sep 2014, Rick Jones wrote:
>
>> Well, there has been such a thing present in TCP from "The Beginning"
>> though not named as such.  Such a client could always advertise a
>> smaller (initial) receive window...  One which would allow only IW3 or
>> whatever value was appropriate.
>
> I'm sure there are ways to solve this, but my take from the "TCP people"
> was that there was not seen to be any need to do anything else than what
> is done today, ie all TCP connections are self contained and learns
> nothing from each other.

Well, I cannot speak for "TCP people" but I would think that what a 
given TCP connection decides to advertise as its receive window, and 
whether that decision would need/must depend on what other TCP 
connections have seen are separate, but related.

The main point I wished to make was if one did indeed wish to have a 
receiver behind a slow pipe wish to be able to keep a sender up on a 
fast pipe from actually doing IW10, there was no need for any new signal 
flowing from one end to the other, just setting the receive window 
appropriately.  The TCP stack on the slow-connection device could (and 
perhaps should) be configured for things like (initial) receive windows 
with that in mind.

rick jones

  reply	other threads:[~2014-09-25 17:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 23:33 Dave Taht
2014-09-20  9:03 ` Steinar H. Gunderson
2014-09-20 15:55   ` Jonathan Morton
2014-09-20 16:47     ` Michael Welzl
2014-09-23  5:48 ` Mikael Abrahamsson
2014-09-23  8:31   ` Jonathan Morton
2014-09-25  4:16   ` David Lang
2014-09-25  5:32     ` Mikael Abrahamsson
2014-09-25  7:35       ` David Lang
2014-09-25  8:08         ` Mikael Abrahamsson
2014-09-25 11:00           ` David Lang
2014-09-25 13:00             ` Mikael Abrahamsson
2014-09-25 13:25               ` Dave Taht
2014-09-25 14:35                 ` Mikael Abrahamsson
2014-09-25 16:09       ` Rick Jones
2014-09-25 17:26         ` Mikael Abrahamsson
2014-09-25 17:49           ` Rick Jones [this message]
2014-09-27  8:59             ` Manolis Sifalakis
2014-09-29 17:28               ` Rick Jones
2014-10-04 19:56                 ` Manolis Sifalakis

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=542455BB.70608@hp.com \
    --to=rick.jones2@hp.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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