WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sbin/sysctl?h=master 2021-01-13T16:28:49Z 2021-01-13T16:28:49Z cheloha cheloha@openbsd.org 2021-01-13T16:28:49Z urn:sha1:9589ba9d8c337eade22f8e39fd77554e71d63034 The global "tickadj" variable is a remnant of the old NTP adjustment code we used in the kernel before the current timecounter subsystem was imported from FreeBSD circa 2004 or 2005. Fifteen years hence it is completely vestigial and we can remove it. We probably should have removed it long ago but I guess it slipped through the cracks. FreeBSD removed it in 2002: https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d NetBSD and DragonflyBSD can probably remove it, too. We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2 and sysctl(8) accordingly. Hypothetically this change could break someone's sysctl(8) parsing script. I don't think that's very likely. ok mvs@ 2020-12-28T18:29:44Z mglocker mglocker@openbsd.org 2020-12-28T18:29:44Z urn:sha1:1b800d6d45f9acdefd5e26f97292c82e6e056b13 ok mpi@ 2020-11-17T12:11:04Z mglocker mglocker@openbsd.org 2020-11-17T12:11:04Z urn:sha1:94043e77226de2539ea5c3bf8bc847047e140889 2020-07-15T07:13:56Z kettenis kettenis@openbsd.org 2020-07-15T07:13:56Z urn:sha1:e8afce5b5b9d68772098e66f10777f7b6abb530d used by the processor chip. Although we have a SENSOR_WATTHOUR sensor type its units are not really suitable for this sensor. So add a SENSOR_ENERGY type that uses micro Joules as its unit. ok deraadt@ 2020-05-29T04:42:23Z deraadt deraadt@openbsd.org 2020-05-29T04:42:23Z urn:sha1:c8f27247b9f5f282483daaddbfd1267ad73569c5 conversion steps). it only contains kernel prototypes for 4 interfaces, all of which legitimately belong in sys/systm.h, which are already included by all enqueue_randomness() users. 2019-12-25T00:15:36Z cheloha cheloha@openbsd.org 2019-12-25T00:15:36Z urn:sha1:b4dcb8dabafe0fa347a55b06697a3b6cc4d9e64a This flag is set whenever a timeout is put on the wheel and cleared upon (a) running, (b) deletion, and (c) readdition. It serves two purposes: 1. Facilitate distinguishing scheduled and rescheduled timeouts. When a timeout is put on the wheel it is "scheduled" for a later softclock(). If this happens two or more times it is also said to be "rescheduled". The tos_rescheduled value thus indicates how many distant timeouts have been cascaded into a lower wheel level. 2. Eliminate false late timeouts. A timeout is not late if it is due before softclock() has had a chance to schedule it. To track this we need additional state, hence a new flag. rprocter@ raises some interesting questions. Some answers: - This interface is not stable and name changes are possible at a later date. - Although rescheduling timeouts is a side effect of the underlying implementation, I don't forsee us using anything but a timeout wheel in the future. Other data structures are too slow in practice, so I doubt that the concept of a rescheduled timeout will be irrelevant any time soon. - I think the development utility of gathering these sorts of statistics is high. Watching the distribution of timeouts under a given workflow is informative. ok visa@ 2019-11-28T16:27:25Z guenther guenther@openbsd.org 2019-11-28T16:27:25Z urn:sha1:68acdce2ce14b5d52a5ee2f45dad5ea9199c1c0b 2019-10-29T04:20:36Z dlg dlg@openbsd.org 2019-10-29T04:20:36Z urn:sha1:9ce244b65a3e4dc02516f1a55b1a23d180e36e0c 2019-09-22T01:16:39Z krw krw@openbsd.org 2019-09-22T01:16:39Z urn:sha1:68b06bbaa27e7f63fc7a66eeb65f743b9005b60b to ps(1). Noted by kettenis@. florian@'s fix pointed out by maestre@. ok maestre@ 2019-07-12T00:04:59Z cheloha cheloha@openbsd.org 2019-07-12T00:04:59Z urn:sha1:31e91f6b3e7614a02994944161a2cc05c79af7e1 With these totals one can track the throughput of the timeout(9) layer from userspace. With input from mpi@. ok mpi@