Date: Wed, 23 Jan 2019 12:41:09 -0800 From: Freddie Cash <fjwcash@gmail.com> To: "Scheffenegger, Richard" <Richard.Scheffenegger@netapp.com> Cc: "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: RFC8312 Cubic Message-ID: <CAOjFWZ5khCCW2PUFqLceJF%2BPm1FxPOwTHasKogUtYBkXB2JUxA@mail.gmail.com> In-Reply-To: <SN4PR0601MB3728AC1A0E08DEF47B0EA3C686990@SN4PR0601MB3728.namprd06.prod.outlook.com> References: <SN4PR0601MB3728AC1A0E08DEF47B0EA3C686990@SN4PR0601MB3728.namprd06.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 23, 2019 at 12:34 PM Scheffenegger, Richard < Richard.Scheffenegger@netapp.com> wrote: > Hi, > > we encounted an issue with the BSD11 cubic implementation during testing, > when dealing with app-stalled and app-limited traffic patterns. > > The gist is, that at least in the after_idle cong_func for cubic, the > states for ssthresh and cubic epoch time are not reset, leading to > excessive cwnd values (overflows even) and self-inflicted drops due to > dramatic burst transmissions. > > Bug Report, or Patch directly to Phabricator (when it is fully qualified)? > Search the freebsd-stable mailing list archives for the thread with subject line: HEADS UP: TCP CUBIC Broken on 12.0-RELEASE/STABLE https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090255.html An Errata Notice should be going out sometime this month-ish. -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5khCCW2PUFqLceJF%2BPm1FxPOwTHasKogUtYBkXB2JUxA>