<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sbin/sysctl/sysctl.c, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sbin/sysctl/sysctl.c?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sbin/sysctl/sysctl.c?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-05-29T04:42:23Z</updated>
<entry>
<title>dev/rndvar.h no longer has statistical interfaces (removed during various</title>
<updated>2020-05-29T04:42:23Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2020-05-29T04:42:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c8f27247b9f5f282483daaddbfd1267ad73569c5'/>
<id>urn:sha1:c8f27247b9f5f282483daaddbfd1267ad73569c5</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>timeout(9): new flag: TIMEOUT_SCHEDULED, new statistic: tos_scheduled</title>
<updated>2019-12-25T00:15:36Z</updated>
<author>
<name>cheloha</name>
<email>cheloha@openbsd.org</email>
</author>
<published>2019-12-25T00:15:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b4dcb8dabafe0fa347a55b06697a3b6cc4d9e64a'/>
<id>urn:sha1:b4dcb8dabafe0fa347a55b06697a3b6cc4d9e64a</id>
<content type='text'>
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@
</content>
</entry>
<entry>
<title>ks_mapblocks is gone</title>
<updated>2019-11-28T16:27:25Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2019-11-28T16:27:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=68acdce2ce14b5d52a5ee2f45dad5ea9199c1c0b'/>
<id>urn:sha1:68acdce2ce14b5d52a5ee2f45dad5ea9199c1c0b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mobileip is going to the attic</title>
<updated>2019-10-29T04:20:36Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2019-10-29T04:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=9ce244b65a3e4dc02516f1a55b1a23d180e36e0c'/>
<id>urn:sha1:9ce244b65a3e4dc02516f1a55b1a23d180e36e0c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Let sysctl(1) work in single-user mode. Same diff applied by florian@</title>
<updated>2019-09-22T01:16:39Z</updated>
<author>
<name>krw</name>
<email>krw@openbsd.org</email>
</author>
<published>2019-09-22T01:16:39Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=68b06bbaa27e7f63fc7a66eeb65f743b9005b60b'/>
<id>urn:sha1:68b06bbaa27e7f63fc7a66eeb65f743b9005b60b</id>
<content type='text'>
to ps(1).

Noted by kettenis@. florian@'s fix pointed out by maestre@.

ok maestre@
</content>
</entry>
<entry>
<title>sysctl(2): add KERN_TIMEOUT_STATS: timeout(9) status and statistics.</title>
<updated>2019-07-12T00:04:59Z</updated>
<author>
<name>cheloha</name>
<email>cheloha@openbsd.org</email>
</author>
<published>2019-07-12T00:04:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=31e91f6b3e7614a02994944161a2cc05c79af7e1'/>
<id>urn:sha1:31e91f6b3e7614a02994944161a2cc05c79af7e1</id>
<content type='text'>
With these totals one can track the throughput of the timeout(9) layer
from userspace.

With input from mpi@.

ok mpi@
</content>
</entry>
<entry>
<title>wire up net.link.ifrxq.pressure_return and pressure_drop</title>
<updated>2019-07-03T10:32:33Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2019-07-03T10:32:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5243d0ad7b6ceb70e8aa1400bd66f118a7d94714'/>
<id>urn:sha1:5243d0ad7b6ceb70e8aa1400bd66f118a7d94714</id>
<content type='text'>
ok visa@ deraadt@
</content>
</entry>
<entry>
<title>When system calls indicate an error they return -1, not some arbitrary</title>
<updated>2019-06-28T13:32:41Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-06-28T13:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=df69c215c7c66baf660f3f65414fd34796c96152'/>
<id>urn:sha1:df69c215c7c66baf660f3f65414fd34796c96152</id>
<content type='text'>
value &lt; 0.  errno is only updated in this case.  Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
</content>
</entry>
<entry>
<title>Restrict filesystem access to read only _PATH_DEVDB and /dev through unveil(2),</title>
<updated>2019-06-16T09:30:15Z</updated>
<author>
<name>mestre</name>
<email>mestre@openbsd.org</email>
</author>
<published>2019-06-16T09:30:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c753220d8c9a23a85e2c14a962cf769dbb25105d'/>
<id>urn:sha1:c753220d8c9a23a85e2c14a962cf769dbb25105d</id>
<content type='text'>
discussed by many.
Additionally call ctime(3) before unveil(2) in order to avoid potential $TZ
expansion and therefore avoiding opening more files that would need to be read,
idea from deraadt@.
While here sort the headers alphabetically.

OK florian@ deraadt@
</content>
</entry>
<entry>
<title>KERN_PFSTATUS is not handled by sysctl so warn about it if requested but</title>
<updated>2019-05-13T20:47:19Z</updated>
<author>
<name>claudio</name>
<email>claudio@openbsd.org</email>
</author>
<published>2019-05-13T20:47:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4696cb9b821ab87c3ca393e159b26a29672663fb'/>
<id>urn:sha1:4696cb9b821ab87c3ca393e159b26a29672663fb</id>
<content type='text'>
ignore if sysctl -a is used.
OK bluhm@
</content>
</entry>
</feed>
