Date: Sun, 24 Feb 2019 06:32:21 -0500 From: Randall Stewart <rrs@netflix.com> To: Michael Tuexen <tuexen@freebsd.org> Cc: "Scheffenegger, Richard" <Richard.Scheffenegger@netapp.com>, "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org> Subject: Re: DSACK Message-ID: <F75B74B6-752F-4F6A-886A-E00A484E051E@netflix.com> In-Reply-To: <5AD822A0-06D7-44DB-AFB1-2453FD59A222@freebsd.org> References: <SN4PR0601MB3728752D55B7231BC4CF22B586780@SN4PR0601MB3728.namprd06.prod.outlook.com> <5ACAD39A-2A77-43BB-BE93-994C1C6C93AB@freebsd.org> <SN4PR0601MB3728DDE5402768567DA9415F86780@SN4PR0601MB3728.namprd06.prod.outlook.com> <5AD822A0-06D7-44DB-AFB1-2453FD59A222@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I don=E2=80=99t think I have ever seen FreeBSD emit a DSACK. Now = admittedly I have only paid close attention in current. But that spans even back into 11 days I think. Hmm wonder if I have a 10 machine I can go back and look at :) R > On Feb 23, 2019, at 5:30 AM, Michael Tuexen <tuexen@freebsd.org> = wrote: >=20 >> On 23. Feb 2019, at 11:28, Scheffenegger, Richard = <Richard.Scheffenegger@netapp.com> wrote: >>=20 >>=20 >> Bin grad am flughafen und hab leider nur HEAD bei mir (und ein iso = von 10, wo ich grad versuch, das mit scapy zu checken). >>=20 >> Falls du schnell einen packetdrill gegen BSD11 ohne D18960 machen = kannst, und es da noch DSACKs raussendet, w=C3=A4re das toll! >>=20 >> Ich f=C3=BCrchte aber, das das schon l=C3=A4ngere Zeit kaputt ist - = da wir nun doch noch nicht D18960 drinnen haben, wie ich irrt=C3=BCmlich = dachte. > OK. I'll take a look. >=20 > Have a save trip! >=20 > Best regards > Michael >>=20 >>=20 >>=20 >> -----Original Message----- >> From: Michael Tuexen <tuexen@freebsd.org>=20 >> Sent: Samstag, 23. Februar 2019 11:25 >> To: Scheffenegger, Richard <Richard.Scheffenegger@netapp.com> >> Cc: freebsd-transport@freebsd.org >> Subject: Re: DSACK >>=20 >> NetApp Security WARNING: This is an external email. Do not click = links or open attachments unless you recognize the sender and know the = content is safe. >>=20 >>=20 >>=20 >>=20 >>> 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. >>=20 >> Best regards >> Michael >>>=20 >>> Thanks a lot, >>> Richard >>>=20 >>=20 >=20 > _______________________________________________ > freebsd-transport@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-transport > To unsubscribe, send any mail to = "freebsd-transport-unsubscribe@freebsd.org" ------ Randall Stewart rrs@netflix.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F75B74B6-752F-4F6A-886A-E00A484E051E>