From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [Make-wifi-fast] WireGuard Queuing, Bufferbloat, Performance, Latency, and related issues
Date: Fri, 30 Sep 2016 20:13:02 -0000 [thread overview]
Message-ID: <CAHmME9pyrW=wRUmXLJhnyO=_Fp=s_oxeJuqcHgQPse=tY0_BjQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4BXgjTgEAUyBnDE05PgdsNp0FOUNxvi3sUhM5F-6KRdQ@mail.gmail.com>
Hi all,
On Fri, Sep 30, 2016 at 9:18 PM, Dave Taht <dave.taht@gmail.com> 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
next prev parent reply other threads:[~2016-09-30 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHmME9pT3wYc=zCm7XcBcgnsT2pDrNWQZpS95+d=GoPPQLa5VQ@mail.gmail.com>
2016-09-30 19:18 ` Dave Taht
2016-09-30 20:13 ` Jason A. Donenfeld [this message]
2016-09-30 23:21 Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9pyrW=wRUmXLJhnyO=_Fp=s_oxeJuqcHgQPse=tY0_BjQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox