Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Jim Gettys <jg@freedesktop.org>, Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Bufferbloat in 3G/4G
Date: Mon, 17 Dec 2012 10:55:05 -0800	[thread overview]
Message-ID: <20121217105505.05eeed00@nehalam.linuxnetplumber.net> (raw)

Injong Rhee pointed me to this paper published at IMC.
  http://research.csc.ncsu.edu/netsrv/sites/default/files/p329.pdf

Interesting tidbit is yet another hack to avoid bufferbloat.

"Our investigation into the open source Android
platform reveals that a small untold trick has been
applied to mitigate the issue: the maximum TCP receive
buffer size parameter (tcp rmem max) has been set to a relatively
small value although the physical buffer size is much
larger. Since the advertised receive window (rwnd) cannot
exceed the receive buffer size and the sender cannot send
more than what is allowed by the advertised receive window,
the limit on tcp rmem max effectively prevents TCP
congestion window (cwnd) from excessive growth and controls
the RTT (round trip time) of the flow within a reasonable
range. However, since the limit is statically configured,
it is sub-optimal in many scenarios, especially considering
the dynamic nature of the wireless mobile environment.

They propose doing receiver adjustment which might help avoid
the "big buffer is at my stupid ISP" problem.

"In this paper, we propose dynamic receive
window adjustment (DRWA), a light-weight, receiver-based
solution that is cheap to deploy. Since DRWA requires modifications
only on the receiver side and is fully compatible
with existing TCP protocol, carriers or device manufacturers
can simply issue an over-the-air (OTA) update to smart
phones so that they can immediately enjoy better performance
even when interacting with existing servers.

Is anyone interested in integrating and testing this?

                 reply	other threads:[~2012-12-17 18:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=20121217105505.05eeed00@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jg@freedesktop.org \
    /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