Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Osku Sneits <wireguard@sneits.fi>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: freebsd - cpu consumption?
Date: Wed, 14 Apr 2021 14:21:28 -0600	[thread overview]
Message-ID: <CAHmME9pRkZasYNM-DGYtTLTzwV6yiWygwhDCkFwZcb2KS-v9UA@mail.gmail.com> (raw)
In-Reply-To: <CAH_zGLXZ1TNMBsv3XZJnhX=TPNqiNL+DiC6icMyx+YcL3rbAnQ@mail.gmail.com>

Hi Osku,

We'll switch to using FreeBSD's opencrypto at some point, at which
point the performance will improve. Right now we're using boring
unoptimized reference implementations.

See https://lists.freebsd.org/pipermail/freebsd-hackers/2021-March/057076.html
for more info. So far nobody has stepped up to contribute code there.

Jason

      reply	other threads:[~2021-04-14 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 18:00 Osku Sneits
2021-04-14 20:21 ` 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=CAHmME9pRkZasYNM-DGYtTLTzwV6yiWygwhDCkFwZcb2KS-v9UA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \
    --cc=wireguard@sneits.fi \
    /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).