Date: Sat, 23 Feb 2019 11:25:26 +0100 From: Michael Tuexen <tuexen@freebsd.org> To: "Scheffenegger, Richard" <Richard.Scheffenegger@netapp.com> Cc: "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org> Subject: Re: DSACK Message-ID: <5ACAD39A-2A77-43BB-BE93-994C1C6C93AB@freebsd.org> In-Reply-To: <SN4PR0601MB3728752D55B7231BC4CF22B586780@SN4PR0601MB3728.namprd06.prod.outlook.com> References: <SN4PR0601MB3728752D55B7231BC4CF22B586780@SN4PR0601MB3728.namprd06.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 23. Feb 2019, at 10:29, Scheffenegger, Richard = <Richard.Scheffenegger@netapp.com> wrote: >=20 > Hi, >=20 > A colleague pointed me to the stack (HEAD) no longer emitting DSACK = options a few days ago... >=20 > I was under the impression, that older versions of FreeBSD would send = out DSACKs for spurious duplicate packets. >=20 > But when I try this script against HEAD, regular cumulative ACKs = without DSACK blocks are showing up. >=20 > Currently bandwidth starved - but was that a conscious decision? Or = was me observing DSACKs never a thing? I would say if it is working in stable/11, but not in stable/12 and = head, it is a regression. Best regards Michael >=20 > Thanks a lot, > Richard >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ACAD39A-2A77-43BB-BE93-994C1C6C93AB>