Date: Mon, 26 Sep 2022 15:28:52 -0400 From: Alexander Motin <mav@FreeBSD.org> To: Ivan Quitschal <tezeka@hotmail.com>, Hans Petter Selasky <hps@selasky.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "freebsd-usb@FreeBSD.org" <freebsd-usb@FreeBSD.org> Subject: Re: RES: TP-LINK USB no carrier after speed test Message-ID: <d863a8ec-edfd-73bc-c772-216830e0d7d5@FreeBSD.org> In-Reply-To: <CP6P284MB1900A6E8ECDB4CFF78323904CB529@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> References: <CP6P284MB1900F16EDAEAF1CB485BC372CB499@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <CP6P284MB1900CF5B403F7F8BE7DD5857CB499@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <de8c944a-59b7-1fb0-e8bf-0f4c31d95090@selasky.org> <5c9c47d6-9e12-ae76-ce67-15aeae1b8636@selasky.org> <11b7de01-d95e-5280-2a22-8b17e29c34c0@selasky.org> <CP5P284MB1902026EB918E88DE5581ACCCB489@CP5P284MB1902.BRAP284.PROD.OUTLOOK.COM> <5f646a9a-2885-05af-9ff1-ef4c4446f365@selasky.org> <CP5P284MB1902929145200C5BE706C789CB489@CP5P284MB1902.BRAP284.PROD.OUTLOOK.COM> <9c370afb-1931-f977-16a9-4915a82ec773@selasky.org> <CP5P284MB19020B7054012F9140E9D8F2CB489@CP5P284MB1902.BRAP284.PROD.OUTLOOK.COM> <CP6P284MB19005F8AF0CF964D011E8EA7CB4A9@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <fd261e3f-ed98-1c48-2af2-943520acbf13@selasky.org> <5bf98c30-c00f-7e7a-3a3d-c0bd5862fb97@selasky.org> <CP6P284MB1900A6E8ECDB4CFF78323904CB529@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM>
index | next in thread | previous in thread | raw e-mail
Ivan, On 26.09.2022 13:11, Ivan Quitschal wrote: > bad news im afraid, problem occurred at the first attempt on speedtest.net. > and I'm really trying to help you analizying this code here myself, but > problem is: im far from expert on network protocol business. if it is a > network problem at all. seems to me more like a USB protocol limit issue > or something .. just FYI , limiting that first constant to 2048 still > limits my upload to 90mbps , and also still solves the issue .. there > has to be something about it obviously On my tests I found that reduction of URE_MAX_TX from 4 to 1 actually help a lot more without so dramatic performance decrease. Though it is likely only a workaround and does not explain the cause, so I hope Hans more ideas for us to test. ;) -- Alexander Motinhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d863a8ec-edfd-73bc-c772-216830e0d7d5>