wireguard-openbsd/lib/libc/sys/msync.2, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/sys/msync.2?h=jd%2Fqueueboosts2019-12-21T05:23:38ZIn "4.2BSD System Manual" (/usr/doc/sysman in 4.2BSD source)2019-12-21T05:23:38Zjsgjsg@openbsd.org2019-12-21T05:23:38Zurn:sha1:7d5edd4cc6f59d1e5b4cc1506903a97ced9ba2c9
mmap(), munman(), madvise() and mprotect() are described as planned for
later releases.
A fully functional mmap(2) supporting shared libraries first appeared in
SunOS 4.0 along with msync(2). SunOS 4.1 added madvise(3) and replaced
msync(2) with mctl(2) which was was used to implement msync(3), mlock(3)
and munlock(3).
While some of these functions appear as empty or ifdef'd functions in
4.1cBSD and later it was not until the Mach VM was integrated with Net/2
that most of them were implemented. Though the CSRG releases never
supported shared libraries or madvise(). mlock()/munlock() were not in
Net/2 as they were added by hibler in 1993, but were in 4.4BSD.
madvise(2) was implemented for UVM in NetBSD 1.5 and ported to
OpenBSD 2.7.
For now instead of trying to accurately describe when interfaces
first appeared in other systems correct when they were first available
in CSRG or OpenBSD releases, retaining the text in mmap(2) discussing
SunOS 4.0.
madvise(2) 4.4BSD -> OpenBSD 2.7
mmap2(2) 4.4BSD -> 4.3BSD Net/2
mprotect(2) 4.4BSD -> 4.3BSD Net/2
msync(2) 4.4BSD -> 4.3BSD Net/2
munmap(2) 4.1cBSD -> 4.3BSD Net/2
The msync interface first appeared in SunOS 4.0.2019-12-10T00:49:26Zjsgjsg@openbsd.org2019-12-10T00:49:26Zurn:sha1:47686af2f44ba73c18a4b38523b32cc29071a342mincore() is a relic from the past, exposing physical machine information2019-01-11T18:46:30Zderaadtderaadt@openbsd.org2019-01-11T18:46:30Zurn:sha1:54e4f6b9a1dc183e1dc7c4a722c2646aa309246a
about shared resources which no program should see. only a few pieces of
software use it, generally poorly thought out. they are being fixed, so
mincore() can be deleted.
ok guenther tedu jca sthen, others
update text to be more like posix, in particular wrt length = 02015-10-29T12:03:46Ztedutedu@openbsd.org2015-10-29T12:03:46Zurn:sha1:9c203acb3021937027ea81f4f950c6235b0d256cremove the first comma from constructs like ", and," and ", or,": you can use2015-03-13T19:58:40Zjmcjmc@openbsd.org2015-03-13T19:58:40Zurn:sha1:0870f47d288c1d823f37828d4fce83d3773e2fc7
"and" and "or" to join sentence clauses, and you can use commas, but both hinders
reading;
Various small typographic fixes for mman.h manual pages:2014-07-02T22:22:35Zmatthewmatthew@openbsd.org2014-07-02T22:22:35Zurn:sha1:2d1971724ef73d66215c6ed70d21fe807b28b014
Use .Fn instead of .Nm as appropriate
Use .In for include lines
Use .Rv -std where possible
Use .Xr to refer to functions from other manual pages
Remove extraneous sys/types.h include
More substantive changes to follow.
Discussed with schwarze
Don't use use .Tn with AND/OR/NOT2014-02-13T07:30:39Zguentherguenther@openbsd.org2014-02-13T07:30:39Zurn:sha1:3fe753f8ad80d65104a976295facaeb57ca3d49f
Phrase any "The _flags_ argument is the ..." line consistently,
eliminating unnecessary use of 'inclusive' and saying "zero or more"
or "one or more" as appropriate
ok millert@ jmc@ schwarze@
convert to new .Dd format;2007-05-31T19:19:00Zjmcjmc@openbsd.org2007-05-31T19:19:00Zurn:sha1:9490d37cb6a2f9c8feb8d4b7f9c43b2ac41784aaNow that the code is consistent, make the descriptions of EINVAL2007-02-26T07:44:06Zottootto@openbsd.org2007-02-26T07:44:06Zurn:sha1:89a87f4b47dbe688ac9e5862ba35184e903844fc
consisten also. ok millert@ jmc@
Missing colons.2005-09-12T20:06:26Zmiodmiod@openbsd.org2005-09-12T20:06:26Zurn:sha1:95f4bbd5676a2cf011ff4e26da4f531840598ed0