From: "Toke Høiland-Jørgensen" <toke@toke.dk>
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: [WireGuard] [Cake] WireGuard Queuing, Bufferbloat, Performance, Latency, and related issues
Date: Sat, 01 Oct 2016 17:51:30 +0200 [thread overview]
Message-ID: <87ponk9if1.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4MCXRn2zfqw3yuckD5YSsRCRUmLqC9VP88q9ODTLv5ng@mail.gmail.com> (Dave Taht's message of "Sat, 1 Oct 2016 08:40:59 -0700")
Dave Taht <dave.taht@gmail.com> writes:
> My thought - given that at least on some platforms - encrypting 1000
> packets at a time is a bad idea - would be something regulating the
> amount of data being crypted at a time, an equivalent to byte queue
> limits - BQL - BCL? byte crypto limits - to keep no more than, say,
> 1ms of data in that part of the subsystem.
Well, the dynamic queue limit stuff is reusable (in
include/linux/dynamic_queue_limits.h). The netdev BQL stuff just uses
these functions with the packet byte sizes; so adapting it to use in
wireguard should be fairly straight forward :)
> ... also pulling stuff out of order from an already encrypted thing
> leads to the same IV problems we had in mac80211.
Yeah, but who needs IVs, really? ;)
-Toke
next prev parent reply other threads:[~2016-10-01 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 23:21 [WireGuard] " Jason A. Donenfeld
2016-10-01 11:51 ` [WireGuard] [Cake] " Toke Høiland-Jørgensen
2016-10-01 15:40 ` Dave Taht
2016-10-01 15:51 ` Toke Høiland-Jørgensen [this message]
2016-10-01 17:19 ` Dave Taht
2016-10-01 17:28 ` Toke Høiland-Jørgensen
2016-10-01 22:44 ` Jason A. Donenfeld
2016-10-01 23:40 ` Toke Høiland-Jørgensen
2016-10-02 2:25 ` Jason A. Donenfeld
2016-10-02 2:40 ` Jason A. Donenfeld
2016-10-02 11:31 ` Toke Høiland-Jørgensen
2016-10-05 12:39 ` Jason A. Donenfeld
2016-10-05 13:59 ` Toke Høiland-Jørgensen
2016-10-05 14:21 ` Jonathan Morton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ponk9if1.fsf@toke.dk \
--to=toke@toke.dk \
--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;
as well as URLs for NNTP newsgroup(s).