From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Hal Murray <hmurray@megapathdsl.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] SO_SNDBUF and SO_RCVBUF
Date: Thu, 23 Apr 2015 22:23:32 -0700 [thread overview]
Message-ID: <1429853012.22254.119.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAA93jw7cWb6-F-AV-GD8CvFVCQ-zXaTZ_UnByOGpdo_O93A8Ng@mail.gmail.com>
On Thu, 2015-04-23 at 21:37 -0700, Dave Taht wrote:
> On Wed, Apr 22, 2015 at 2:05 PM, Rick Jones <rick.jones2@hp.com> wrote:
> > On 04/22/2015 02:02 PM, Eric Dumazet wrote:
> >>
> >> Yeah, the real nice thing is TCP_NOTSENT_LOWAT added in linux-3.12
>
> I will argue that that would give a much better estimate as to how
> much data was really outstanding on the wire.
This would be the responsibility of the CC.
Each CC has its own ways to be controlled. vegas & cubic have different
knobs.
TCP_NOTSENT_LOWAT controls the number of unsent bytes. This is generic.
You do not want to add a 'knob' that would lock all CC to a given
behavior : It is already there with pacing.
If you know the rtt, then with pacing you also can limit XXX bytes on
the wire.
next prev parent reply other threads:[~2015-04-24 5:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 19:10 Hal Murray
2015-04-22 19:26 ` Rick Jones
2015-04-22 19:28 ` Dave Taht
2015-04-22 21:02 ` Eric Dumazet
2015-04-22 21:05 ` Rick Jones
2015-04-22 21:46 ` Eric Dumazet
2015-04-22 22:20 ` Simon Barber
2015-04-22 23:08 ` Eric Dumazet
2015-04-24 4:37 ` Dave Taht
2015-04-24 4:40 ` Dave Taht
2015-04-24 13:50 ` Eric Dumazet
2015-04-24 14:34 ` Dave Taht
2015-04-24 16:31 ` Rick Jones
2015-04-24 18:41 ` Eric Dumazet
2015-04-24 5:23 ` Eric Dumazet [this message]
2015-04-22 21:07 ` Steinar H. Gunderson
2015-04-22 21:42 ` Eric Dumazet
2015-04-22 21:47 ` Dave Taht
2015-04-22 22:11 ` Steinar H. Gunderson
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=1429853012.22254.119.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=hmurray@megapathdsl.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