From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id EF2213B2AE; Fri, 30 Sep 2016 16:13:01 -0400 (EDT) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 0b90785b; Fri, 30 Sep 2016 20:02:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; s=mail; bh=yaEAS0s/beJ9RRDIHbyrdGk+GGA=; b=gk9Aj2 gkQoKCXDBeMVpltqbzsXWxmoRLcwKTowlyZ3gtSgpXfW5mGQzjYB5gaEw96+8u7L YG7C6X6cF3DiraxIGXQWvRh4RJD1qW/ZXZTym14a5HshpEzh6YVk3YsI5OyecFEt 7cOQ5TcVlIoklEMVjbVgnwTZrTcn5UCi6JHOhm6K28eN8zNRROuqqig+k0xIM/fv EgiRxraqxACvx7+Xa6t6i2Lcmty1+Vn90FqJuEPm+UjwGTef1Fjg47sIffYu/dg5 gC6dwjbkHPYtZ7JNyyZ3vujiQoLxooXhiqeGqV5+bByPH56cYN3U3CaDTU4k2gF8 J8wBtlKq3Fl0hO2w== Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 2261b6e5 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO); Fri, 30 Sep 2016 20:02:14 +0000 (UTC) Received: by mail-lf0-f54.google.com with SMTP id t81so48503159lfe.0; Fri, 30 Sep 2016 13:13:00 -0700 (PDT) X-Gm-Message-State: AA6/9RmLYeofodoRo++DiYJWcjDeUF/WgrX9K5mNDnRAOR12FKHJr4cWJ0meL006rfMu8NLfOOv7hiM1LKjEqQ== X-Received: by 10.25.160.6 with SMTP id j6mr4139514lfe.159.1475266378825; Fri, 30 Sep 2016 13:12:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.159.16 with HTTP; Fri, 30 Sep 2016 13:12:58 -0700 (PDT) In-Reply-To: References: From: "Jason A. Donenfeld" X-Gmail-Original-Message-ID: Message-ID: To: Dave Taht Cc: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net, WireGuard mailing list Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Mon, 28 Nov 2016 08:47:10 -0500 Subject: Re: [Make-wifi-fast] WireGuard Queuing, Bufferbloat, Performance, Latency, and related issues X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Fri, 30 Sep 2016 20:13:02 -0000 X-Original-Date: Fri, 30 Sep 2016 22:12:58 +0200 X-List-Received-Date: Fri, 30 Sep 2016 20:13:02 -0000 Hi all, On Fri, Sep 30, 2016 at 9:18 PM, Dave Taht wrote: > All: I've always dreamed of a vpn that could fq and - when it was > bottlenecking on cpu - throw away packets intelligently. Wireguard, > which is what jason & co are working on, is a really simple, elegant > set of newer vpn ideas that currently has a queuing model designed to > optimize for multi-cpu encryption, and not, so much, for managing > worst case network behaviors, or fairness, or working on lower end > hardware. Would love any feedback and support for working on the queuing model with WireGuard. I hear the bufferbloat folks are geniuses at that... > Do do a git clone of the code, and take a look... somewhere on the > wireguard list, or privately, jason'd pointed me at the relevant bits > of the queuing model. It was this post: https://lists.zx2c4.com/pipermail/wireguard/2016-August/000378.html Start reading from "There are a couple reasons" and finish at "chunking them somehow." The rest can be disregarded. Hope to hear from y'all soon! Thanks, Jason