From: Lev Stipakov <lstipakov@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Volatile in Wintun
Date: Wed, 21 Aug 2019 16:14:53 +0300 [thread overview]
Message-ID: <CAGyAFMUYDP3fXx4tvaCW+SLvPYSWeRV-+gUNc=9HBsWweCOOTQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pOPkhYnE2D7-RhSVyECosL8NcrhsAL05C9SPSYiqVG5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 345 bytes --]
Hi Jason,
we don't assume that volatile implies a memory
> barrier. We could probably switch to /volatile:iso.
>
Does it mean that hardware reordering like writes reordered after reads
on x86/amd64 and everything else on ARM are not considered to be a problem?
Should barriers generated by WaitForSingleObject / SetEvent be enough?
--
-Lev
[-- Attachment #1.2: Type: text/html, Size: 731 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-21 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 7:26 Lev Stipakov
2019-08-19 18:15 ` Jason A. Donenfeld
2019-08-21 13:14 ` Lev Stipakov [this message]
2019-08-24 12:41 ` 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='CAGyAFMUYDP3fXx4tvaCW+SLvPYSWeRV-+gUNc=9HBsWweCOOTQ@mail.gmail.com' \
--to=lstipakov@gmail.com \
--cc=Jason@zx2c4.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).