From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dave Taht <dave@taht.net>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"WireGuard list" <wireguard@lists.zx2c4.com>
Subject: Re: ARM multitheaded?
Date: Thu, 23 Nov 2017 00:20:47 +0100 [thread overview]
Message-ID: <CAHmME9o-K3j-cso8ZWDZNLJWW=a9=VkK23gw0mvXwdr-WFrosg@mail.gmail.com> (raw)
In-Reply-To: <878texyk9e.fsf@nemesis.taht.net>
On Thu, Nov 23, 2017 at 12:19 AM, Dave Taht <dave@taht.net> wrote:
> Not moi? :)
You too, of course!
>
> My take on things was basically not even try to do multicore on single
> flows but to start by divvying up things into tons of queues, and try to
> keep those flows entirely on the core they started with.
Yes, this is the traditional approach taken, but it doesn't work well
for accelerating the crypto of say, a single file downloading or
somebody watching youtube. I don't want these pegged to a single core.
Jason
prev parent reply other threads:[~2017-11-22 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 9:25 René van Dorst
2017-11-21 9:40 ` René van Dorst
2017-11-21 10:02 ` Jason A. Donenfeld
[not found] ` <878texyk9e.fsf@nemesis.taht.net>
2017-11-22 23:20 ` Jason A. Donenfeld [this message]
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='CAHmME9o-K3j-cso8ZWDZNLJWW=a9=VkK23gw0mvXwdr-WFrosg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dave@taht.net \
--cc=toke@toke.dk \
--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).