From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 0B2543B29D; Thu, 25 Feb 2021 05:30:08 -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=1614249003; bh=QXAiek6o8SM/gpxaGclCbQD4i8+2Ar5cDa+mBUGl7wc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hG1hdq2TYkNXEBWe2/xpY8hA42yoej88HWpiEnLJvXtwFrbRPvvJkvzRj40wxE5SD hG6lkDiYegRcyldtZAbzxLt3j/Le6X/3kdbnIHHU/xj9gGk/lQynq/kmeCX3vUY0Hl ZPLYjHHpzc8n/WY8frQT/gtjcJetdgdk3OLE2l/n8Qb/mmn4kI7SyOPz9jM2nxpJMU RVDN041OX05LCJBuwiHeaH7dVy62U53gn6leI2OwqERV8naXytK8Syc0D2WYvQbr8z Pzi1Uq2kLNNdQGAwjkMxyfqgQYj5WLtHXctK9tbwKXQuBDkXqqa+72DVspdZc6Us0a gNnexBxDWYg6g== To: Nils Andreas Svee , Dave Taht Cc: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= via Cake , Make-Wifi-fast , cerowrt-devel , bloat , Simon Sundberg In-Reply-To: <90a13934-4ec7-4872-bbf8-c6c0f6304ce3@www.fastmail.com> References: <874ki24ref.wl-jch@irif.fr> <1e41ddf7-cd08-4fec-b31a-3021f8111dc6@www.fastmail.com> <87im6h4u2p.fsf@toke.dk> <369A70AB-3ADF-4211-8A09-E9FB77CEE59D@toke.dk> <90a13934-4ec7-4872-bbf8-c6c0f6304ce3@www.fastmail.com> Date: Thu, 25 Feb 2021 11:30:03 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87wnuw1luc.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] [Bloat] Fwd: [Galene] Dave on bufferbloat and jitter at 8pm CET Tuesday 23 X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 10:30:08 -0000 "Nils Andreas Svee" writes: > I ran it on my router though, which has a decent amount of TCP flows running at any given time. > It's all going over a wg tunnel though, that might be wonky for all I > know. Ah, wireguard doesn't have XDP support, so that's likely not going to work; and if you run it on the physical interface, even if you didn't get driver errors, the tool would just see the encrypted packets which is not terribly helpful (it parses TCP timestamps to match incoming/outgoing packets and compute the RTT). I guess we should be more flexible about which hooks we support, so it can also be used on devices with no XDP support. Adding in Simon, who is writing the code; I think he is focused on getting a couple of other features done first, but this could go on the TODO list :) -Toke