From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 75F803B29E for ; Sun, 19 Nov 2017 11:29:06 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1511108942; bh=DVA6YYliCcbs8GFGphWwQBCLKArTvc3pXCSMhEAOkPI=; h=From:To:Subject:In-Reply-To:References:Date:From; b=i+Gk1L5ZsUl8zjJfO9SSlXK3Di9pqJUbXaePbDmh7abWvQUqaDAG6ZreNW9TtrB1j xyFriSyKDaBVxjn2gmVCLJP123pKJH4lj8TBOV/yn393//hvSjHWWRXdqB2Lwg4Mdc JVudbHC/lV8Aw3+XVvW+H1G7iozdxevFWqbhXQ78RIeDMSD3g+ALSO+j1p4Gbu+Xo0 ikQpAMuINbI9JsAwxW9rC5BqnhrefH9mjW1s0XyCyCGZlVjuUddgFT6Yd0WG6YH7gj +IEFvLITMkmNCjXyeaewg4VZeYaAxlW7rcmyP/vpPSIkmoh479zfh317b7RIbV8itX RDb9E0IlwzSuA== To: Caleb Cushing , bloat@lists.bufferbloat.net In-Reply-To: References: Date: Sun, 19 Nov 2017 17:28:33 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <8760a6b5ce.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain 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 16:29:06 -0000 Caleb Cushing writes: > I've actually managed to get game streaming mostly smooth, but there's > still an occasional stutter (latency increase from ~5ms to around > 100ms, then it goes away again) that I haven't figured out. happy to > provide more information if it'll help this use case. note, the > additional options mentioned in the forum on src/desthost seem to > actually make things worse. 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. 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. -Toke