From: Roman Mamedov <rm@romanrm.net>
To: Lee Yates <rainmakerraw@icloud.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Logical cores / SMT with WireGuard
Date: Sun, 17 Feb 2019 15:54:08 +0500 [thread overview]
Message-ID: <20190217155408.3c6b8590@natsu> (raw)
In-Reply-To: <735c8b20-c92b-2403-1557-32187b130a8f@icloud.com>
On Thu, 14 Feb 2019 18:02:26 +0000
Lee Yates <rainmakerraw@icloud.com> wrote:
> recommendations to disable HT, I got to wondering how much - if at all -
> disabling HT would impact on WireGuard's real world performance. I mean,
> it obviously can utilise logical cores/threads, but is there a real
> world throughput benefit vs just using the real cores?
This sounds like something YOU are in a great position to test, and then write
an interesting blog post or mailing list message summarising the results. :)
--
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-02-17 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 18:02 Lee Yates
2019-02-17 10:54 ` Roman Mamedov [this message]
2019-02-17 11:01 ` Roman Mamedov
2019-02-17 20:44 ` Tom Li
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=20190217155408.3c6b8590@natsu \
--to=rm@romanrm.net \
--cc=rainmakerraw@icloud.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).