From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] What is wrong with Microsoft's receive window auto-tuning?
Date: Thu, 11 Sep 2014 19:40:37 +0200 [thread overview]
Message-ID: <20140911174037.GA22515@sesse.net> (raw)
In-Reply-To: <1410455146.7106.55.camel@edumazet-glaptop2.roam.corp.google.com>
On Thu, Sep 11, 2014 at 10:05:46AM -0700, Eric Dumazet wrote:
>> Is anyone aware of any research either pointing out how their tuning
>> algorithm works, or of known bugs/problems with the algorithm?
> How BDP suggests a receive window of 750k ?
>
> If BDP _is_ 750k, then 3.8 MB receive window is not insane, it depends
> on the amount of drops and how fast you want to recover from drops.
If it helps, I've seen problems in Linux' auto-tuning as well, so this is
seemingly a hard problem :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2014-09-11 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 17:23 Jerry Jongerius
2014-09-11 17:05 ` Eric Dumazet
2014-09-11 17:40 ` Steinar H. Gunderson [this message]
2014-09-11 21:13 ` Eric Dumazet
2014-09-12 11:03 ` Jerry Jongerius
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=20140911174037.GA22515@sesse.net \
--to=sgunderson@bigfoot.com \
--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