From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 8E5C53B29E for ; Sun, 19 Nov 2017 16:19:10 -0500 (EST) Received: by mail-lf0-x235.google.com with SMTP id 73so7911559lfu.10 for ; Sun, 19 Nov 2017 13:19:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1eCHe40iSTPuIlFW6jtozDpuhp+n+DPIpi38ZYHUx48=; b=vRT67xMVqIX2nUlq5GN19XKHTqSEhETD3V7+h5YtbMf/7B/CjTLhBAil27uyfSNSpL M8QWo+aD+tcyh3nZkQqHExnIGV/ISi5o1GuNsNDLmuKun5aalbPtKk8fN7ngwRyv9i4K Nbh3BKapj+kXM2zPJXKfg9QTM+6Y5TuODX8O6mdThUvRkqJ9pvv98AiJPjccLGYYXqBz ZyENvBeSvrwviVXjqS7BPypEAnFyOgtz2t4cp18fLonHeez0o//+2zZzJ+ZG32HXYtd9 zBwHpTRsmj4RyIetcy2oRjm7hKG5ePk4H9jFggjkTZhbzBcIJuoz/9Yekx3i0BB+l2Bx /R0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1eCHe40iSTPuIlFW6jtozDpuhp+n+DPIpi38ZYHUx48=; b=qa4e3XqRnU7LOmgxh9ckA1Mgm2aknFkOe2D5R7PEkSqRtU/Ql7Cdc86Tq+RsHjwhrD Hr98jhN453yFXn5Glbq5EGeMknwmTSI1lm8vEUvn7h/7lUjzL7Ua+Y7zNRPXaaR877TW OddmGAv9Dmh0bS2q0Q9hwdmTeQC+z5jZcA0jUMCXQpyYOtsSldykOJbvjBiLmztVWo5T +tW1YQ8kswrUQ8orrYi9JPeLPPIZDjDTRMogpFFx0Ep6UItMq+t0W95HZXZeNJvIkGQv Bxpa4uLbtT8pYTW+t0VQ+WHFH3Z1/tzsV/iiSlYR6luryfaznMG1wvnq0fNdN4DeFGkP Eyug== X-Gm-Message-State: AJaThX4y+HSej6IhrOZUvGQLaLyv4C2vAwjEW5L0zf70f6dKfil03NXz sYn4T6ZfiDB0Ot/lbKldNGv/n4AtOLgawTD4gMo= X-Google-Smtp-Source: AGs4zMZAbc67SIPnfpEZxYnayAQbVdjsEdb6GQ0dEtR+1rBULYssU93DIb759tMH16x/FJNDe03GXP9nXn81/5yu6BE= X-Received: by 10.25.79.79 with SMTP id a15mr2607616lfk.246.1511126349292; Sun, 19 Nov 2017 13:19:09 -0800 (PST) MIME-Version: 1.0 References: <8760a6b5ce.fsf@toke.dk> In-Reply-To: <8760a6b5ce.fsf@toke.dk> From: Caleb Cushing Date: Sun, 19 Nov 2017 21:18:58 +0000 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="94eb2c1cdb0a42a9f6055e5c8570" Subject: Re: [Bloat] Steam In Home Streaming on ath9k wifi X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Nov 2017 21:19:10 -0000 --94eb2c1cdb0a42a9f6055e5c8570 Content-Type: text/plain; charset="UTF-8" > > > So this is two computers talking to each other over WiFi? What > chipsets/drivers are they using for WiFi? It may very well be that what > you're seeing is hickups in the WiFi connection at the computer, not at > the router. In which case there's nothing you can do on the router to > fix it. > sure possible, can't say it's not, I did manage to find a channel that only I'm on in the 5 ghz range and all machines are within 2 meters of the AP. But of course it's wifi so, no real guarantees. Both computers are running windows 10. Server is running a qualcomm device says it's using the killer wireless n/a/c version 4.0.2.26 (fishy, I know killer wireless is sort of it's own qos, I think I've effectively disabled it though). Client is running an Intel Dual Band wireless AC 8260, driver 19.71.1.1. > > Another possibility is that it's an occasional signal drop that causes > excessive retries (either at the router or the AP). We have not gotten > around to limiting the retries in the drivers yet, so that can cause > quite a bit of very intermittent head of line blocking as well. > > could also be, do those retries happen when it's udp? 'cause I think steam homestreaming is basically all udp, maybe the packets are just getting dropped? -- Caleb Cushing http://xenoterracide.com --94eb2c1cdb0a42a9f6055e5c8570 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
So this is two computers talking to each other over WiFi? What
chipsets/drivers are they using for WiFi? It may very well be that what
you're seeing is hickups in the WiFi connection at the computer, not at=
the router. In which case there's nothing you can do on the router to fix it.

sure possible, can't say it= 's not, I did manage to find a channel that only I'm on in the 5 gh= z range and all machines are within 2 meters of the AP. But of course it= 9;s wifi so, no real guarantees.

Both computers are running windows = 10. Server is running a qualcomm device says it's using the killer wire= less n/a/c version 4.0.2.26 (fishy, I know killer wireless is sort of it= 9;s own qos, I think I've effectively disabled it though). Client is ru= nning an Intel Dual Band wireless=C2=A0AC 8260, driver=C2=A019.71.1.1.
= =C2=A0

Another possibility is that it's an occasional signal drop that causes<= br> excessive retries (either at the router or the AP). We have not gotten
around to limiting the retries in the drivers yet, so that can cause
quite a bit of very intermittent head of line blocking as well.

could also be, do those retries happen when it's udp? = 9;cause I think steam homestreaming is basically all udp, maybe the packets= are just getting dropped?=C2=A0
--
<= /div>
Caleb Cushing

--94eb2c1cdb0a42a9f6055e5c8570--