wireguard-openbsd/share, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/share?h=jd%2Fqueueboosts2020-06-22T21:16:07Ztimecounting: add gettime(9), getuptime(9)2020-06-22T21:16:07Zchelohacheloha@openbsd.org2020-06-22T21:16:07Zurn:sha1:8dca5d44636110d0ff0cfe71785c8f18da7ca99e
time_second and time_uptime are used widely in the tree. This is a
problem on 32-bit platforms because time_t is 64-bit, so there is a
potential split-read whenever they are used at or below IPL_CLOCK.
Here are two replacement interfaces: gettime(9) and getuptime(9).
The "get" prefix signifies that they do not read the hardware
timecounter, i.e. they are fast and low-res. The lack of a unit
(e.g. micro, nano) signifies that they yield a plain time_t.
As an optimization on LP64 platforms we can just return time_second or
time_uptime, as a single read is atomic. On 32-bit platforms we need
to do the lockless read loop and get the values from the timecounter.
In a subsequent diff these will be substituted for time_second and
time_uptime almost everywhere in the kernel.
With input from visa@ and dlg@.
ok kettenis@
provide missing Aq; this one started my search for missing Aq, then i failed2020-06-21T15:26:39Zjmcjmc@openbsd.org2020-06-21T15:26:39Zurn:sha1:3c002c406f860118ea0f93e0ac735f6e4a5a3a2b
to commit it...
new sentence, new line;2020-06-21T15:25:30Zjmcjmc@openbsd.org2020-06-21T15:25:30Zurn:sha1:b38c59c9bd22e6102655cc962c3b90b297ca2018various minor tweaks;2020-06-21T15:23:59Zjmcjmc@openbsd.org2020-06-21T15:23:59Zurn:sha1:ade9e6ce83b64399de12612825a443c2f9ab419badd a manpage for wg(4).2020-06-21T12:25:47Zdlgdlg@openbsd.org2020-06-21T12:25:47Zurn:sha1:28057f2d0d00f0a3ef161f2bfa475468c79b6a3b
the mandoc linter is upset about "An Jason A. Donenfeld", but i'm
hoping ingo or jmc will fix it for me :)
From Matt Dunwoodie
ok deraadt@
wireguard is taking over the gif mbuf tag.2020-06-21T11:44:12Zdlgdlg@openbsd.org2020-06-21T11:44:12Zurn:sha1:87c66d4c756ebd51dd0ade264773d56d0702e2cc
gif used its mbuf tag to store it's interface index so it could
detect loops. gre also did this, and i cut most of the drivers
(including gif) over to using the gre tag. so the gif tag is unused.
wireguard uses the tag to store peer information between different
contexts the packet is processed in. it also needs a bit more space
to do that.
from Matt Dunwoodie and Jason A. Donenfeld
ok deraadt@
document mq_push()2020-06-21T05:43:48Zdlgdlg@openbsd.org2020-06-21T05:43:48Zurn:sha1:5d717772933521b3c73d9006c79a1fff6f30cb9fsupply the Aq (angle brackets) part missing in:2020-06-20T21:16:14Zjmcjmc@openbsd.org2020-06-20T21:16:14Zurn:sha1:d918c33ea4b77a9dc42bb4617d9ec931897f6a99
.An author Aq Mt address
bcmtmon(4)2020-06-20T18:19:26Zketteniskettenis@openbsd.org2020-06-20T18:19:26Zurn:sha1:9a712520a6626833b9db48e67161bb8fbdd10687stoeplitz_to_key takes a void * now.2020-06-19T08:50:59Zdlgdlg@openbsd.org2020-06-19T08:50:59Zurn:sha1:7c2acd1668fcb3499d1325b92990e508b2798fad