Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg KH <greg@kroah.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Performance of Wireguard on Infiniband 40G
Date: Sun, 14 May 2017 12:49:59 +0200	[thread overview]
Message-ID: <CAHmME9rxGD6gWoW0Q71YN4dn_J4bRD7rk1x_2ihgb0sn0r4Dbw@mail.gmail.com> (raw)
In-Reply-To: <20170514104817.GA29758@kroah.com>

Hey Greg,

On Sun, May 14, 2017 at 12:48 PM, Greg KH <greg@kroah.com> wrote:
> 4.9 is 6 months old, I'd be curious if 4.11 is any faster given the rate
> of change in the network stack :)

I imagine it might be. I think the biggest bottle neck, in any case,
is still the poor algorithm in padata. Hopefully we'll get this sorted
with the help of Samuel's research this summer!

Jason

  reply	other threads:[~2017-05-14 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  7:37 Baptiste Jonglez
2017-05-13 22:52 ` Jason A. Donenfeld
2017-05-14  9:55   ` Baptiste Jonglez
2017-05-14 10:48     ` Greg KH
2017-05-14 10:49       ` Jason A. Donenfeld [this message]
2017-05-13 23:45 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHmME9rxGD6gWoW0Q71YN4dn_J4bRD7rk1x_2ihgb0sn0r4Dbw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=greg@kroah.com \
    --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).