From: Jaume Barcelo <jaume.barcelo@upf.edu>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] sweet tcp
Date: Tue, 9 Jul 2013 19:38:40 +0200 [thread overview]
Message-ID: <CAJpd8ptg46TmHk=cFECAqspXctW_OwnBc8ORf7Sbo1cUoThScg@mail.gmail.com> (raw)
Hi,
I was explaining the bufferbloat problem to some undergrad students
showing them the "Bufferbloat: Dark Buffers in the Internet" paper. I
asked them to find a solution for the problem and someone pointed at
Fig. 1 and said "That's easy. All you have to do is to operate in the
sweet point where the throughput is maximum and the delay is minimum".
It seemed to me that it was a good idea and I tried to think a way to
force TCP to operate close to the optimal point. The goal is to
increase the congestion window until it is larger than the optimal
one. At that point, start decreasing the congestion window until is
lower than the optimal point.
To be more specific, TCP would be at any time increasing or decreasing
the congestion window. In other words, it will be moving in one
direction (right or left) along the x axis of Fig. 1 of Getty's paper.
Each RTT, the performance is measured in terms of delay and
throughput. If there is a performance improvement, we keep moving in
the same direction. If there is a performance loss, we change the
direction.
I tried to explain the algorithm here:
https://github.com/jbarcelo/sweet-tcp-paper/blob/master/document.pdf?raw=true
I am not an expert on TCP, so I decided to share it with this list to
get some expert opinions.
Thanks,
Jaume
next reply other threads:[~2013-07-09 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 17:38 Jaume Barcelo [this message]
2013-07-09 17:56 ` Stephen Hemminger
2013-07-09 19:10 ` Eric Dumazet
2013-07-09 19:33 ` Hannes Frederic Sowa
2013-07-09 21:37 ` Jaume Barcelo
2013-07-16 1:15 ` Lawrence Stewart
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='CAJpd8ptg46TmHk=cFECAqspXctW_OwnBc8ORf7Sbo1cUoThScg@mail.gmail.com' \
--to=jaume.barcelo@upf.edu \
--cc=bloat@lists.bufferbloat.net \
/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