Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@newmedia-net.de>
To: wireguard@lists.zx2c4.com
Subject: Re: iOS WG (1.0.3) - ARM64 SIMD ChaCha20
Date: Thu, 21 Feb 2019 18:09:56 +0100	[thread overview]
Message-ID: <9c33c6e4-5631-18de-24c0-49b5c6f58aa6@newmedia-net.de> (raw)
In-Reply-To: <1E89DB79-1BB3-4279-B13D-1321235D9BE5@lonnie.abelbeck.com>


Am 21.02.2019 um 17:03 schrieb Lonnie Abelbeck:
>
>> On Feb 20, 2019, at 3:01 PM, Sebastian Gottschall <s.gottschall@newmedia-net.de> wrote:
>>
>>
>> Am 20.02.2019 um 16:03 schrieb Lonnie Abelbeck:
>>> Thanks to Jason and the team, a new iOS WG 1.0.3 appeared as an update:
>>>
>>> 1.0.3 / Feb 19, 2019
>>> --
>>> Performance should be higher and battery usage lower, thanks to a new ARM64 SIMD implementation of ChaCha20
>>> --
>>> For reference, the upstream golang crypto commit is here [1] with performance numbers.
>>>
>>> So, the question come to mind, do my iOS devices have ARM64 SIMD support, quick answer is if the device is less than 6 years old it should have ARM64 SIMD support.  Added in the A5/A6 CPU's from what I can tell.
>> A5 and A6 is 32 bit. A7 was the first 64 bit cpu (introduced with Iphone 5s)
>>
>> Sebastian
> Thanks Sebastian for the info,
>
> It appears if the device can run iOS 12 (required by iOS WG) then it also has ARM64 SIMD support.
yes. because all 32 bit systems are unsupported anyway. so there is no 
32 bit wg version available since you cannot submit them to apple since 
a along time
if i remember correct 32 bit support stopped with ios 10.
>
> Lonnie
>
>
>
>>> Apple-designed processors
>>> https://en.wikipedia.org/wiki/Apple-designed_processors
>>>
>>> [1] chacha20: add SIMD implementation on arm64
>>> https://go.googlesource.com/crypto/+/74369b46fc6756741c016591724fd1cb8e26845f
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-02-21 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 15:03 Lonnie Abelbeck
2019-02-20 21:01 ` Sebastian Gottschall
2019-02-21 16:03   ` Lonnie Abelbeck
2019-02-21 17:09     ` Sebastian Gottschall [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=9c33c6e4-5631-18de-24c0-49b5c6f58aa6@newmedia-net.de \
    --to=s.gottschall@newmedia-net.de \
    --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).