d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
513575d446
freebsd-skq/share/man/man9/Makefile

2386 lines
67 KiB
Makefile
Raw Normal View History

$Id$ -> $FreeBSD$
1999-08-28 00:22:10 +00:00
# $FreeBSD$
Add a section 9 about the kernel to out man pages. Please help fill this out !
1995-12-14 10:08:31 +00:00
Clean up more usb related files when MK_USB == no when dealing with manpages, libraries, and binaries
2014-11-26 21:18:52 +00:00
.include <src.opts.mk>
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MAN= accept_filter.9 \
accf_data.9 \
Add a man page for the DNS accept filter.
2008-07-18 14:46:01 +00:00
accf_dns.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
accf_http.9 \
acl.9 \
alq.9 \
Add altq(9) explaining about the IFQ_* and IFQ_DRV_* macros in if_var.h and how to convert drivers. Obtained from: NetBSD (with changes) Reviewed by: josef
2004-08-07 12:35:56 +00:00
altq.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
atomic.9 \
bhnd(4) update inline documentation comments and man pages. This includes a number of copyedits for the inline code documentation comments, updates to the existing bhnd(4), bhndb(4), bcma(4), and siba(4) man pages, and new man pages for bhnd_chipc(4), bhnd_pmu(4), bhndb_pci(4), bhnd(9), and bhnd_erom(9). Approved by: adrian (mentor) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D13021
2017-11-27 21:30:49 +00:00
bhnd.9 \
bhnd_erom.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bios.9 \
Document bitset(9)
2015-10-17 19:55:58 +00:00
bitset.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
boot.9 \
Add a man page for the kernel part of bpf. I made some edits to the man page after Orla, so the mistakes are probably mine. Leave a note on the door welcoming the mdoc police. Submitted by: Orla McGann <orly@cnri.dit.ie>
2004-05-19 20:39:22 +00:00
bpf.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
buf.9 \
Manpages for the buf_ring and drbr interfaces. Submitted by: kmacy (aeons ago) MFC after: 1 week
2012-01-30 21:02:25 +00:00
buf_ring.9 \
Add manpages for BUF_RECURSED(9) and BUF_ISLOCKED(9) and connect them to the build. Reviewed by: brueffer
2008-01-22 21:26:35 +00:00
BUF_ISLOCKED.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
BUF_LOCK.9 \
BUF_LOCKFREE.9 \
BUF_LOCKINIT.9 \
Add manpages for BUF_RECURSED(9) and BUF_ISLOCKED(9) and connect them to the build. Reviewed by: brueffer
2008-01-22 21:26:35 +00:00
BUF_RECURSED.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
BUF_TIMELOCK.9 \
BUF_UNLOCK.9 \
bus_activate_resource.9 \
The DEVICE_IDENTIFY man page refers to this, create a dummy one directing people to device_add_child.
2004-05-13 20:28:18 +00:00
BUS_ADD_CHILD.9 \
Add a new bus method, BUS_ADJUST_RESOURCE() that is intended to be a wrapper around rman_adjust_resource(). Include a generic implementation, bus_generic_adjust_resource() which passes the request up to the parent bus. There is currently no default implementation. A bus_adjust_resource() wrapper is provided for use in drivers.
2011-04-29 21:36:45 +00:00
bus_adjust_resource.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_alloc_resource.9 \
Add a manual page for BUS_BIND_INTR() and bus_bind_intr(). MFC after: 1 week
2009-10-14 15:58:59 +00:00
BUS_BIND_INTR.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_child_present.9 \
Add a BUS_CHILD_DELETED() method that a bus can hook to allow it to cleanup any bus-specific state (such as ivars) when a child device is deleted. Requested by: kan MFC after: 1 month
2012-08-21 18:13:09 +00:00
BUS_CHILD_DELETED.9 \
Add a manpage for BUS_CHILD_DETACHED().
2012-08-21 18:41:38 +00:00
BUS_CHILD_DETACHED.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
BUS_CONFIG_INTR.9 \
Create new wrapper function: bus_delayed_attach_children() Delay the attachment of children, when requested, until after interrutps are running. This is often needed to allow children to run transactions on i2c or spi busses. It's a common enough idiom that it will be useful to have its own wrapper. Reviewed by: ian Differential Revision: https://reviews.freebsd.org/D21465
2019-12-13 19:39:33 +00:00
bus_delayed_attach_children.9 \
Add a facility for associating optional descriptions with active interrupt handlers. This is primarily intended as a way to allow devices that use multiple interrupts (e.g. MSI) to meaningfully distinguish the various interrupt handlers. - Add a new BUS_DESCRIBE_INTR() method to the bus interface to associate a description with an active interrupt handler setup by BUS_SETUP_INTR. It has a default method (bus_generic_describe_intr()) which simply passes the request up to the parent device. - Add a bus_describe_intr() wrapper around BUS_DESCRIBE_INTR() that supports printf(9) style formatting using var args. - Reserve MAXCOMLEN bytes in the intr_handler structure to hold the name of an interrupt handler and copy the name passed to intr_event_add_handler() into that buffer instead of just saving the pointer to the name. - Add a new intr_event_describe_handler() which appends a description string to an interrupt handler's name. - Implement support for interrupt descriptions on amd64 and i386 by having the nexus(4) driver supply a custom bus_describe_intr method that invokes a new intr_describe() MD routine which in turn looks up the associated interrupt event and invokes intr_event_describe_handler(). Requested by: many Reviewed by: scottl MFC after: 2 weeks
2009-10-15 14:54:35 +00:00
BUS_DESCRIBE_INTR.9 \
Add the bus_dma(9) manual page to our section 9 collection. It provides comprehensive documentation on FreeBSD's Bus DMA interface. Approved by: gibbs, re@ (scottl) Reviewed by: gibbs, scottl, des, sam, jake, tmm
2003-05-30 22:57:54 +00:00
bus_dma.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_generic_attach.9 \
Removed garbage: - bus_generic_map_intr.9. This has been undead for more than 3 years following the changes in rev.1.4 of sys/bus.h. - CONDSPLASSERT.9, SPLASSERT.9. These have been undead since SMPng. They were even less useful than most section 9 man pages -- the interfaces described in them have never been used in the FreeBSD source tree.
2001-10-04 09:46:01 +00:00
bus_generic_detach.9 \
Add support for multiple passes of the device tree during the boot-time probe. The current device order is unchanged. This commit just adds the infrastructure and ABI changes so that it is easier to merge later changes into 8.x. - Driver attachments now have an associated pass level. Attachments are not allowed to probe or attach to drivers until the system-wide pass level is >= the attachment's pass level. By default driver attachments use the "last" pass level (BUS_PASS_DEFAULT). Driver's that wish to probe during an earlier pass use EARLY_DRIVER_MODULE() instead of DRIVER_MODULE() which accepts the pass level as an additional parameter. - A new method BUS_NEW_PASS has been added to the bus interface. This method is invoked when the system-wide pass level is changed to kick off a rescan of the device tree so that drivers that have just been made "eligible" can probe and attach. - The bus_generic_new_pass() function provides a default implementation of BUS_NEW_PASS(). It first allows drivers that were just made eligible for this pass to identify new child devices. Then it propogates the rescan to child devices that already have an attached driver by invoking their BUS_NEW_PASS() method. It also reprobes devices without a driver. - BUS_PROBE_NOMATCH() is only invoked for devices that do not have an attached driver after being scanned during the final pass. - The bus_set_pass() function is used during boot to raise the pass level. Currently it is only called once during root_bus_configure() to raise the pass level to BUS_PASS_DEFAULT. This has the effect of probing all devices in a single pass identical to previous behavior. Reviewed by: imp Approved by: re (kib)
2009-06-09 14:26:23 +00:00
bus_generic_new_pass.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_generic_print_child.9 \
bus_generic_read_ivar.9 \
bus_generic_shutdown.9 \
Add a new bus method to fetch device-specific CPU sets. bus_get_cpus() returns a specified set of CPUs for a device. It accepts an enum for the second parameter that indicates the type of cpuset to request. Currently two valus are supported: - LOCAL_CPUS (on x86 this returns all the CPUs in the package closest to the device when DEVICE_NUMA is enabled) - INTR_CPUS (like LOCAL_CPUS but only returns 1 SMT thread for each core) For systems that do not support NUMA (or if it is not enabled in the kernel config), LOCAL_CPUS fails with EINVAL. INTR_CPUS is mapped to 'all_cpus' by default. The idea is that INTR_CPUS should always return a valid set. Device drivers which want to use per-CPU interrupts should start using INTR_CPUS instead of simply assigning interrupts to all available CPUs. In the future we may wish to add tunables to control the policy of INTR_CPUS (e.g. should it be local-only or global, should it ignore SMT threads or not). The x86 nexus driver exposes the internal set of interrupt CPUs from the the x86 interrupt code via INTR_CPUS. The ACPI bus driver and PCI bridge drivers use _PXM to return a suitable LOCAL_CPUS set when _PXM exists and DEVICE_NUMA is enabled. They also and the global INTR_CPUS set from the nexus driver with the per-domain set from _PXM to generate a local INTR_CPUS set for child devices. Compared to the r298933, this version uses 'struct _cpuset' in <sys/bus.h> instead of 'cpuset_t' to avoid requiring <sys/param.h> (<sys/_cpuset.h> still requires <sys/param.h> for MAXCPU even though <sys/_bitset.h> does not after recent changes).
2016-05-09 20:50:21 +00:00
BUS_GET_CPUS.9 \
Document bus_get_resource(9). Suggested by: Francois Tigeot Obtained from: DragonFlyBSD 09301a2b29f3ae5edd39a858f909f8770372f71e Sponsored by: EMC / Isilon Storage Division
2015-09-26 14:52:47 +00:00
bus_get_resource.9 \
Add new bus methods for mapping resources. Add a pair of bus methods that can be used to "map" resources for direct CPU access using bus_space(9). bus_map_resource() creates a mapping and bus_unmap_resource() releases a previously created mapping. Mappings are described by 'struct resource_map' object. Pointers to these objects can be passed as the first argument to the bus_space wrapper API used for bus resources. Drivers that wish to map all of a resource using default settings (for example, using uncacheable memory attributes) do not need to change. However, drivers that wish to use non-default settings can now do so without jumping through hoops. First, an RF_UNMAPPED flag is added to request that a resource is not implicitly mapped with the default settings when it is activated. This permits other activation steps (such as enabling I/O or memory decoding in a device's PCI command register) to be taken without creating a mapping. Right now the AGP drivers don't set RF_ACTIVE to avoid using up a large amount of KVA to map the AGP aperture on 32-bit platforms. Once RF_UNMAPPED is supported on all platforms that support AGP this can be changed to using RF_UNMAPPED with RF_ACTIVE instead. Second, bus_map_resource accepts an optional structure that defines additional settings for a given mapping. For example, a driver can now request to map only a subset of a resource instead of the entire range. The AGP driver could also use this to only map the first page of the aperture (IIRC, it calls pmap_mapdev() directly to map the first page currently). I will also eventually change the PCI-PCI bridge driver to request mappings of the subset of the I/O window resource on its parent side to create mappings for child devices rather than passing child resources directly up to nexus to be mapped. This also permits bridges that do address translation to request suitable mappings from a resource on the "upper" side of the bus when mapping resources on the "lower" side of the bus. Another attribute that can be specified is an alternate memory attribute for memory-mapped resources. This can be used to request a Write-Combining mapping of a PCI BAR in an MI fashion. (Currently the drivers that do this call pmap_change_attr() directly for x86 only.) Note that this commit only adds the MI framework. Each platform needs to add support for handling RF_UNMAPPED and thew new bus_map/unmap_resource methods. Generally speaking, any drivers that are calling rman_set_bustag() and rman_set_bushandle() need to be updated. Discussed on: arch Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D5237
2016-05-20 17:57:47 +00:00
bus_map_resource.9 \
Add support for multiple passes of the device tree during the boot-time probe. The current device order is unchanged. This commit just adds the infrastructure and ABI changes so that it is easier to merge later changes into 8.x. - Driver attachments now have an associated pass level. Attachments are not allowed to probe or attach to drivers until the system-wide pass level is >= the attachment's pass level. By default driver attachments use the "last" pass level (BUS_PASS_DEFAULT). Driver's that wish to probe during an earlier pass use EARLY_DRIVER_MODULE() instead of DRIVER_MODULE() which accepts the pass level as an additional parameter. - A new method BUS_NEW_PASS has been added to the bus interface. This method is invoked when the system-wide pass level is changed to kick off a rescan of the device tree so that drivers that have just been made "eligible" can probe and attach. - The bus_generic_new_pass() function provides a default implementation of BUS_NEW_PASS(). It first allows drivers that were just made eligible for this pass to identify new child devices. Then it propogates the rescan to child devices that already have an attached driver by invoking their BUS_NEW_PASS() method. It also reprobes devices without a driver. - BUS_PROBE_NOMATCH() is only invoked for devices that do not have an attached driver after being scanned during the final pass. - The bus_set_pass() function is used during boot to raise the pass level. Currently it is only called once during root_bus_configure() to raise the pass level to BUS_PASS_DEFAULT. This has the effect of probing all devices in a single pass identical to previous behavior. Reviewed by: imp Approved by: re (kib)
2009-06-09 14:26:23 +00:00
BUS_NEW_PASS.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
BUS_PRINT_CHILD.9 \
BUS_READ_IVAR.9 \
Add a new rescan method to the bus interface. The BUS_RESCAN() method rescans a single bus device checking for devices that have been added or removed from the bus. A new 'rescan' command is added to devctl(8) to trigger a rescan. Differential Revision: https://reviews.freebsd.org/D6016
2016-04-27 16:29:03 +00:00
BUS_RESCAN.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_release_resource.9 \
Add support for multiple passes of the device tree during the boot-time probe. The current device order is unchanged. This commit just adds the infrastructure and ABI changes so that it is easier to merge later changes into 8.x. - Driver attachments now have an associated pass level. Attachments are not allowed to probe or attach to drivers until the system-wide pass level is >= the attachment's pass level. By default driver attachments use the "last" pass level (BUS_PASS_DEFAULT). Driver's that wish to probe during an earlier pass use EARLY_DRIVER_MODULE() instead of DRIVER_MODULE() which accepts the pass level as an additional parameter. - A new method BUS_NEW_PASS has been added to the bus interface. This method is invoked when the system-wide pass level is changed to kick off a rescan of the device tree so that drivers that have just been made "eligible" can probe and attach. - The bus_generic_new_pass() function provides a default implementation of BUS_NEW_PASS(). It first allows drivers that were just made eligible for this pass to identify new child devices. Then it propogates the rescan to child devices that already have an attached driver by invoking their BUS_NEW_PASS() method. It also reprobes devices without a driver. - BUS_PROBE_NOMATCH() is only invoked for devices that do not have an attached driver after being scanned during the final pass. - The bus_set_pass() function is used during boot to raise the pass level. Currently it is only called once during root_bus_configure() to raise the pass level to BUS_PASS_DEFAULT. This has the effect of probing all devices in a single pass identical to previous behavior. Reviewed by: imp Approved by: re (kib)
2009-06-09 14:26:23 +00:00
bus_set_pass.9 \
Document what bus_set_resource(9) does. It is used by bus drivers to bind resources that client drivers later access.
2003-03-30 00:25:23 +00:00
bus_set_resource.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
BUS_SETUP_INTR.9 \
Don a flack jacket and start to document the FreeBSD bus_space implementation. I took the NetBSD man page, and hacked it to, I hope, to reflect the preliminary version of the bus space that Justin Gibbs committed as part of the CAM integration in FreeBSD 3.0. This isn't perfect, but it is better than we have now (which is, ahem, nothing). Please coordinate changes to the file through me through the 6.0 release. Approved by: re (blanket for this one file)
2005-06-14 03:40:01 +00:00
bus_space.9 \
Create a manual to document the new kernel byte order conversion functions. Reviewed by: tmm
2002-03-06 01:53:35 +00:00
byteorder.9 \
Remove the deprecated timeout(9) interface. All in-tree consumers have been converted to callout(9). Reviewed by: kib, markj Differential Revision: https://reviews.freebsd.org/D22602
2019-12-13 21:03:12 +00:00
callout.9 \
Actually install casuword(9) to fix build.
2014-10-28 16:19:02 +00:00
casuword.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
cd.9 \
Introduce cnv man page. Submitted by: Adam Starak <starak.adam@gmail.com> Reviewed by: cem@, wblock@ Differential Revision: https://reviews.freebsd.org/D7249
2016-08-27 13:47:52 +00:00
cnv.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
condvar.9 \
Document config_intrhook. MFC After: 250 millifortnights
2006-09-25 20:12:13 +00:00
config_intrhook.9 \
Link in contigmalloc(9) to the build.
2004-03-06 08:01:16 +00:00
contigmalloc.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
copy.9 \
Merge from projects/counters: counter(9). Introduce counter(9) API, that implements fast and raceless counters, provided (but not limited to) for gathering of statistical data. See http://lists.freebsd.org/pipermail/freebsd-arch/2013-April/014204.html for more details. In collaboration with: kib Reviewed by: luigi Tested by: ae, ray Sponsored by: Nginx, Inc.
2013-04-08 19:40:53 +00:00
counter.9 \
Document cpuset(9) A follow-up to r289467. Coerced by: jhb Sponsored by: EMC / Isilon Storage Division
2015-10-20 23:48:14 +00:00
cpuset.9 \
Add manuals for cr_cansee(9) and p_cansee(9). Thanks to Ruslan for the time he spent reviewing these. Reviewed by: ru Approved by: ru
2006-11-19 13:35:03 +00:00
cr_cansee.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
critical_enter.9 \
cr_seeothergids.9 \
cr_seeotheruids.9 \
crypto.9 \
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
crypto_asym.9 \
Add support for optional separate output buffers to in-kernel crypto. Some crypto consumers such as GELI and KTLS for file-backed sendfile need to store their output in a separate buffer from the input. Currently these consumers copy the contents of the input buffer into the output buffer and queue an in-place crypto operation on the output buffer. Using a separate output buffer avoids this copy. - Create a new 'struct crypto_buffer' describing a crypto buffer containing a type and type-specific fields. crp_ilen is gone, instead buffers that use a flat kernel buffer have a cb_buf_len field for their length. The length of other buffer types is inferred from the backing store (e.g. uio_resid for a uio). Requests now have two such structures: crp_buf for the input buffer, and crp_obuf for the output buffer. - Consumers now use helper functions (crypto_use_*, e.g. crypto_use_mbuf()) to configure the input buffer. If an output buffer is not configured, the request still modifies the input buffer in-place. A consumer uses a second set of helper functions (crypto_use_output_*) to configure an output buffer. - Consumers must request support for separate output buffers when creating a crypto session via the CSP_F_SEPARATE_OUTPUT flag and are only permitted to queue a request with a separate output buffer on sessions with this flag set. Existing drivers already reject sessions with unknown flags, so this permits drivers to be modified to support this extension without requiring all drivers to change. - Several data-related functions now have matching versions that operate on an explicit buffer (e.g. crypto_apply_buf, crypto_contiguous_subsegment_buf, bus_dma_load_crp_buf). - Most of the existing data-related functions operate on the input buffer. However crypto_copyback always writes to the output buffer if a request uses a separate output buffer. - For the regions in input/output buffers, the following conventions are followed: - AAD and IV are always present in input only and their fields are offsets into the input buffer. - payload is always present in both buffers. If a request uses a separate output buffer, it must set a new crp_payload_start_output field to the offset of the payload in the output buffer. - digest is in the input buffer for verify operations, and in the output buffer for compute operations. crp_digest_start is relative to the appropriate buffer. - Add a crypto buffer cursor abstraction. This is a more general form of some bits in the cryptosoft driver that tried to always use uio's. However, compared to the original code, this avoids rewalking the uio iovec array for requests with multiple vectors. It also avoids allocate an iovec array for mbufs and populating it by instead walking the mbuf chain directly. - Update the cryptosoft(4) driver to support separate output buffers making use of the cursor abstraction. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24545
2020-05-25 22:12:04 +00:00
crypto_buffer.9 \
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
crypto_driver.9 \
crypto_request.9 \
crypto_session.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
CTASSERT.9 \
decription of macros to add ddb commands Submitted by: Guillaume Ballet <gballet@gmail.com> MFC after: 1 month
2008-09-15 23:13:29 +00:00
DB_COMMAND.9 \
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
DECLARE_GEOM_CLASS.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
DECLARE_MODULE.9 \
Hook DEFINE_IFUNC.9 up to the build. Reported by: pluknet MFC with: r348003
2019-05-20 21:23:33 +00:00
DEFINE_IFUNC.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
DELAY.9 \
devclass.9 \
devclass_find.9 \
devclass_get_device.9 \
devclass_get_devices.9 \
Hook up new man page for devclass_get_drivers() to build Reminded by: ru
2005-04-07 17:27:14 +00:00
devclass_get_drivers.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
devclass_get_maxunit.9 \
devclass_get_name.9 \
devclass_get_softc.9 \
Connect dev_clone.9 and devfs_set_cdevpriv.9 to the build.
2008-09-15 10:12:04 +00:00
dev_clone.9 \
devfs_set_cdevpriv.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
device.9 \
device_add_child.9 \
DEVICE_ATTACH.9 \
device_delete_child.9 \
Add man page for device_delete_children. Submitted by: Jeroen Ruigrok van der Werven Differential Revision: https://reviews.freebsd.org/D18452
2019-01-11 19:05:40 +00:00
device_delete_children.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
DEVICE_DETACH.9 \
device_enable.9 \
device_find_child.9 \
device_get_children.9 \
device_get_devclass.9 \
device_get_driver.9 \
device_get_ivars.9 \
device_get_name.9 \
device_get_parent.9 \
device_get_softc.9 \
device_get_state.9 \
Add a stub man page for device_get_sysctl{_ctx,tree}. Needs some work, but is better than nothing. Any help appreciated.
2006-05-23 22:11:20 +00:00
device_get_sysctl.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
device_get_unit.9 \
DEVICE_IDENTIFY.9 \
device_printf.9 \
DEVICE_PROBE.9 \
device_probe_and_attach.9 \
device_quiet.9 \
device_set_desc.9 \
device_set_driver.9 \
device_set_flags.9 \
DEVICE_SHUTDOWN.9 \
DEV_MODULE.9 \
Add a dev_refthread.9 document. Reviewed by: kib Sponsored by: Dell EMC Isilon Differential: https://reviews.freebsd.org/D16897
2018-10-20 20:41:25 +00:00
dev_refthread.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
devstat.9 \
devtoname.9 \
Documentation of kernel disk_create() and disk_destroy() APIs. These APIs permit disk device drivers to register and deregister storage devices for use by storage device consumers. No doubt this API will change more as time flies by, but this should be helpful to the creators of new storage device drivers. Reviewed by: phk
2003-09-26 21:43:25 +00:00
disk.9 \
Add man page for dnvlist. Submitted by: Adam Starak <starak.adam@gmail.com> Reviewed by: cem, wblock
2016-10-05 19:01:00 +00:00
dnv.9 \
Add a man page describing the fuctions directly related to network domains. Reviewed by: alfred
2001-12-07 20:58:07 +00:00
domain.9 \
Implement several enhancements to NUMA policies. Add a new "interleave" allocation policy which stripes pages across domains with a stride or width keeping contiguity within a multi-page region. Move the kernel to the dedicated numbered cpuset #2 making it possible to assign kernel threads and memory policy separately from user. This also eliminates the need for the complicated interrupt binding code. Add a sysctl API for viewing and manipulating domainsets. Refactor some of the cpuset_t manipulation code using the generic bitset type so that it can be used for both. This probably belongs in a dedicated subr file. Attempt to improve the include situation. Reviewed by: kib Discussed with: jhb (cpuset parts) Tested by: pho (before review feedback) Sponsored by: Netflix, Dell/EMC Isilon Differential Revision: https://reviews.freebsd.org/D14839
2018-03-29 02:54:50 +00:00
domainset.9 \
Add a man page for the kernel's dynamic per-CPU memory allocator. MFC after: 3 days
2017-03-26 20:15:08 +00:00
dpcpu.9 \
Manpages for the buf_ring and drbr interfaces. Submitted by: kmacy (aeons ago) MFC after: 1 week
2012-01-30 21:02:25 +00:00
drbr.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
driver.9 \
DRIVER_MODULE.9 \
Add efidev(4)/efirt(9) Document efidev(4), provider of userland access to EFI Runtime Services. A link is created to efirtc(4), which handles the time-of-day clock side. efirt(9) is the kernel side of this. Reviewed by: imp, kib (earlier version) Differential Revision: https://reviews.freebsd.org/D16696
2018-08-17 04:17:51 +00:00
efirt.9 \
Add epoch(9) man page Reviewed by: gallatin@ Approved by: sbruno@
2018-05-13 23:16:04 +00:00
epoch.9 \
Add a manual page for the kernel's EVENTHANDLER facility. Reviewed by: ru
2004-12-03 14:05:55 +00:00
EVENTHANDLER.9 \
Add eventtimers(9) man page, describing related KPIs. Sponsored by: iXsystems, Inc. MFC after: 1 month
2011-12-20 11:40:22 +00:00
eventtimers.9 \
Sort MAN= section.
2001-07-10 07:42:35 +00:00
extattr.9 \
fail(9) support: Add support for kernel fault injection using KFAIL_POINT_* macros and fail_point_* infrastructure. Add example fail point in vfs_bio.c to simulate VM buf pressure. Approved by: dfr (mentor)
2009-05-27 16:36:54 +00:00
fail.9 \
[fdt_pinctrl] Add man pages for fdt_pinctrl driver - Add fdt_pinctrl(4) with general information for the driver - Add fdt_pinctrl(9) with fdt_pinctrl KPI description Reviewed by: ian, manu, wblock MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D14235
2018-03-03 02:49:49 +00:00
fdt_pinctrl.9 \
Whitespace-only change. Tidy up, alphabetise and wrap.
2000-11-21 20:28:48 +00:00
fetch.9 \
firmware(9) is a subsystem to load binary data into the kernel via a specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with this. They include iwi(4), ipw(4), ispfw(4) and digi(4). No objection from: arch MFC after: 2 weeks X-MFC after: some drivers have been converted
2006-01-29 02:52:42 +00:00
firmware.9 \
Add fpu_kern.9 man page to the install. Sponsored by: The FreeBSD Foundation MFC after: 1 week
2014-06-25 07:57:01 +00:00
fpu_kern.9 \
Connect g_access(9) to the build.
2004-03-11 19:51:14 +00:00
g_access.9 \
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
g_attach.9 \
g_bio.9 \
g_consumer.9 \
g_data.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
get_cyclecount.9 \
Add a manpage for the getenv() family of functions in the kernel.
2013-10-22 20:10:38 +00:00
getenv.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
getnewvnode.9 \
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
g_event.9 \
g_geom.9 \
g_provider.9 \
g_provider_by_name.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
groupmember.9 \
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
g_wither_geom.9 \
Connect hash(9) to the build and add MLINKS for all functions. Pointed out by: ru
2006-10-02 11:51:25 +00:00
hash.9 \
Add a manual page for hashinit(9), hashdestroy(9) and phashinit(9). Reviewed by: ru
2004-10-12 02:36:24 +00:00
hashinit.9 \
Add a manual page for the consolidated debugging commit.
2003-12-07 20:48:00 +00:00
hexdump.9 \
Final commit to round out the "Five New TCP Congestion Control Algorithms for FreeBSD" FreeBSD Foundation funded project. - Add new man pages for the modular congestion control, Khelp and Hhook frameworks (cc.4, cc.9, khelp.9 and hhook.9). - Add new man pages for each available congestion control algorithm (cc_chd.4, cc_cubic.4, cc_hd.4, cc_htcp.4, cc_newreno.4 and cc_vegas.4). - Add a new man page for the Enhanced Round Trip Time (ERTT) Khelp module (h_ertt.4). - Update the TCP (tcp.4) man page to mention the TCP_CONGESTION socket option, cross reference to cc.4 and remove references to the retired "net.inet.tcp.newreno" sysctl MIB variable. In collaboration with: David Hayes <dahayes at swin edu au> and Grenville Armitage <garmitage at swin edu au> Sponsored by: FreeBSD Foundation MFC after: 3 months
2011-02-21 11:56:11 +00:00
hhook.9 \
Hook ieee80211 manpages up to the build; fix 1 snafu which crept in. Noticed by: Matthias Schuendehuette Pointy hat to: bms
2004-03-04 21:13:06 +00:00
ieee80211.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_amrr.9 \
ieee80211_beacon.9 \
ieee80211_bmiss.9 \
Hook ieee80211 manpages up to the build; fix 1 snafu which crept in. Noticed by: Matthias Schuendehuette Pointy hat to: bms
2004-03-04 21:13:06 +00:00
ieee80211_crypto.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_ddb.9 \
Hook ieee80211 manpages up to the build; fix 1 snafu which crept in. Noticed by: Matthias Schuendehuette Pointy hat to: bms
2004-03-04 21:13:06 +00:00
ieee80211_input.9 \
ieee80211_node.9 \
ieee80211_output.9 \
ieee80211_proto.9 \
ieee80211_radiotap.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_regdomain.9 \
ieee80211_scan.9 \
ieee80211_vap.9 \
Add a stub manual page for iflib(9). Currently 'man -k iflib' would find you the right pages for iflib documentation, namely iflibdd(9) and iflibdi(9) but 'man iflib' would leave you in the dark. This allows both approaches to find the relevant documentation. Reviewed by: kmacy, shurd Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D15219
2018-05-03 17:52:40 +00:00
iflib.9 \
Add iflib man pages for developers. Doc review is probably waranted here for editing. Submitted by: Nicole Graziano
2017-01-28 00:40:36 +00:00
iflibdd.9 \
iflibdi.9 \
iflibtxrx.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
ifnet.9 \
inittodr.9 \
Add insmntque.9 to the build.
2008-02-26 21:11:05 +00:00
insmntque.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
intro.9 \
ithread.9 \
KASSERT.9 \
Some basic documentation (a man page) on kern_testfrwk
2015-11-12 11:42:01 +00:00
kern_testfrwk.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
kernacc.9 \
Add kernel_mount.9 and appropriate MLINKS to the build.
2004-12-13 19:29:40 +00:00
kernel_mount.9 \
Final commit to round out the "Five New TCP Congestion Control Algorithms for FreeBSD" FreeBSD Foundation funded project. - Add new man pages for the modular congestion control, Khelp and Hhook frameworks (cc.4, cc.9, khelp.9 and hhook.9). - Add new man pages for each available congestion control algorithm (cc_chd.4, cc_cubic.4, cc_hd.4, cc_htcp.4, cc_newreno.4 and cc_vegas.4). - Add a new man page for the Enhanced Round Trip Time (ERTT) Khelp module (h_ertt.4). - Update the TCP (tcp.4) man page to mention the TCP_CONGESTION socket option, cross reference to cc.4 and remove references to the retired "net.inet.tcp.newreno" sysctl MIB variable. In collaboration with: David Hayes <dahayes at swin edu au> and Grenville Armitage <garmitage at swin edu au> Sponsored by: FreeBSD Foundation MFC after: 3 months
2011-02-21 11:56:11 +00:00
khelp.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
kobj.9 \
Doc police fixes thanks to: ru@
2007-10-26 16:50:21 +00:00
kproc.9 \
add man page talking about how to interface w/ the kqueue system so others can write additional filters... mdoc police please!
2006-10-04 20:16:23 +00:00
kqueue.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
kthread.9 \
ktr.9 \
Merged all of the lockmgr functions into a single file (lock.9); as well, some content and layout changes were made. lock.9 had existed before but was never added to Makefile, so it was never installed. That is why the duplicate files were created in the first place. Reviewed by: ru, alfred
2002-01-26 00:09:41 +00:00
lock.9 \
Connect the locking man page to the build. Next step is to add it as a "See Also" to related man pages.
2007-03-30 17:56:19 +00:00
locking.9 \
Fix build (forgotten MUTEX_PROFILING.9 -> LOCK_PROFILING.9).
2006-11-11 08:59:34 +00:00
LOCK_PROFILING.9 \
Document the following MAC policies: o Biba: A data integrity policy o BSD Extended: Support for the firewall-like access controls (ugidfw(8)) o MLS: Multi-level security, a confidentiality policy (These files originally lived in src/share/man/man9) Approved by: re (blanket) Sponsored by: DARPA, Network Associates Labs Obtained from: TrustedBSD Project
2002-12-05 00:05:38 +00:00
mac.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
make_dev.9 \
malloc.9 \
mbchain.9 \
mbuf.9 \
Document mbuf tags based on the OpenBSD manpage. Submitted by: Gleb Smirnoff
2004-05-20 09:34:19 +00:00
mbuf_tags.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MD5.9 \
mdchain.9 \
Fix sloppyness in memcchr() man page. I was considering adding it to libc as well, but last minute I thought it would be good enough to add it to libkern exclusively. I forgot to rename the man page and hook it up.
2012-01-01 20:59:42 +00:00
memcchr.9 \
Connect memguard(9) to the build.
2005-02-22 17:42:12 +00:00
memguard.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
microseq.9 \
microtime.9 \
microuptime.9 \
mi_switch.9 \
Rename the cc.4 and cc.9 modular congestion control related man pages to mod_cc.4 and mod_cc.9 respectively to avoid any possible confusion with the cc.1 gcc man page. Update references to these man pages where required. Requested by: Grenville Armitage Approved by: re (kib) MFC after: 3 days
2011-09-15 12:15:36 +00:00
mod_cc.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
module.9 \
MODULE_DEPEND.9 \
Take a first stab at documenting use of MODULE_PNP_INFO Sponsored by: Dell EMC Isilon
2018-02-12 22:42:06 +00:00
MODULE_PNP_INFO.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MODULE_VERSION.9 \
mtx_pool.9 \
mutex.9 \
Whitespace-only change. Tidy up, alphabetise and wrap.
2000-11-21 20:28:48 +00:00
namei.9 \
Add beginnings of a netisr(9) man page.
2009-06-07 21:31:06 +00:00
netisr.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 \
[man] Add documentation for OpenFirmware API Add man pages for following OpenFirmware functions: OF_child, OF_parent, OF_peer, OF_device_from_xref, OF_device_register_xref, OF_xref_from_device, OF_getprop, OF_getencprop, OF_getencprop_alloc, OF_getprop_alloc, OF_getproplen, OF_hasprop, OF_nextprop, OF_prop_free, OF_searchencprop, OF_searchprop, OF_setprop Edited by: wblock MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D14511
2018-04-09 22:23:45 +00:00
OF_child.9 \
OF_device_from_xref.9 \
OF_finddevice.9 \
OF_getprop.9 \
OF_node_from_xref.9 \
OF_package_to_path.9 \
Document ofw_bus_subr helpers "compatible" and "status" properties Add documentation for following functions: - ofw_bus_is_compatible - ofw_bus_is_compatible_strict - ofw_bus_node_is_compatible - ofw_bus_search_compatible - ofw_bus_get_status - ofw_bus_status_okay - ofw_bus_node_status_okay MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D14724
2018-04-08 20:53:00 +00:00
ofw_bus_is_compatible.9 \
ofw_bus_status_okay.9 \
Add a man page for the Object Specific Data (OSD) KPI. Although not directly related the FreeBSD Foundation funded "Five New TCP Congestion Control Algorithms for FreeBSD" project, the understanding and inspiration required to write this documentation was significantly bolstered by the Foundation's support. Reviewed by: pjd MFC after: 1 week
2011-01-05 11:49:23 +00:00
osd.9 \
New 1-Wire bus implementation. 1-Wire controller is abstracted, though only gpiobus configured via FDT is supported. Bus enumeration is supported. Devices are created for each device found. 1-Wire temperature controllers are supported, but other drivers could be written. Temperatures are polled and reported via a sysctl. Errors are reported via sysctl counters. Mis-wired bus detection is included for more trouble shooting. See ow(4), owc(4) and ow_temp(4) for details of what's supported and known issues. This has been tested on Raspberry Pi-B, Pi2 and Beagle Bone Black with up to 7 devices. Differential Revision: https://reviews.freebsd.org/D2956 Relnotes: yes MFC after: 2 weeks Reviewed by: loos@ (with many insightful comments)
2015-08-27 23:33:38 +00:00
owll.9 \
own.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
panic.9 \
s/PCBGROUPS/PCBGROUP/ manpage to match "options PCBGROUP".
2014-07-22 22:16:23 +00:00
PCBGROUP.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
p_candebug.9 \
Add manuals for cr_cansee(9) and p_cansee(9). Thanks to Ruslan for the time he spent reviewing these. Reviewed by: ru Approved by: ru
2006-11-19 13:35:03 +00:00
p_cansee.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 \
Create a separate kobj interface for leaf-driver PCI IOV methods. Leaf drivers should not import the PCI bus interface to add IOV handling. Instead, move the IOV client methods to a separate kobj interface. Differential Revision: https://reviews.freebsd.org/D2584 Reviewed by: rstone
2015-05-28 22:01:50 +00:00
PCI_IOV_ADD_VF.9 \
PCI_IOV_INIT.9 \
Document the interface for defining a configuration schema Differential Revision: https://reviews.freebsd.org/D89 Reviewed by: wblock, emaste, allanjude MFC after: 1 month Sponsored by: Sandvine Inc.
2015-03-01 00:59:21 +00:00
pci_iov_schema.9 \
Create a separate kobj interface for leaf-driver PCI IOV methods. Leaf drivers should not import the PCI bus interface to add IOV handling. Instead, move the IOV client methods to a separate kobj interface. Differential Revision: https://reviews.freebsd.org/D2584 Reviewed by: rstone
2015-05-28 22:01:50 +00:00
PCI_IOV_UNINIT.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pfil.9 \
pfind.9 \
Documented the pget(9) system kernel interface. Reviewed by: trociny, kib MFC after: 1 week
2014-05-03 18:50:47 +00:00
pget.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pgfind.9 \
Add a manual page for PHOLD() and friends. MFC after: 1 week
2015-11-08 01:41:44 +00:00
PHOLD.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
physio.9 \
pmap.9 \
pmap_activate.9 \
pmap_clear_modify.9 \
pmap_copy.9 \
pmap_enter.9 \
pmap_extract.9 \
pmap_growkernel.9 \
pmap_init.9 \
pmap_is_modified.9 \
pmap_is_prefaultable.9 \
pmap_map.9 \
pmap_mincore.9 \
pmap_object_init_pt.9 \
pmap_page_exists_quick.9 \
Add manual page for newly added pmap_page_init(9) function, part of the PMAP KPI. Reviewed-by: alc
2005-06-10 17:16:16 +00:00
pmap_page_init.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pmap_pinit.9 \
Remove an obsolete man page.
2014-07-18 06:56:24 +00:00
pmap_protect.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pmap_qenter.9 \
Create man page for pmap_quick_enter_page(9) and pmap_quick_remove_page(9) Reviewed by: kib, brueffer, wblock Approved by: kib (mentor) Differential Revision: https://reviews.freebsd.org/D3312
2015-08-07 12:13:15 +00:00
pmap_quick_enter_page.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pmap_release.9 \
pmap_remove.9 \
pmap_resident_count.9 \
Add a man page for the new function pmap_unwire().
2014-07-17 20:03:52 +00:00
pmap_unwire.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pmap_zero_page.9 \
printf.9 \
Document a few kernel functions and the sysctl tunables that affect their behaviour.
2003-12-11 13:29:05 +00:00
prison_check.9 \
Add a new priv(9) kernel interface for checking the availability of privilege for threads and credentials. Unlike the existing suser(9) interface, priv(9) exposes a named privilege identifier to the privilege checking code, allowing more complex policies regarding the granting of privilege to be expressed. Two interfaces are provided, replacing the existing suser(9) interface: suser(td) -> priv_check(td, priv) suser_cred(cred, flags) -> priv_check_cred(cred, priv, flags) A comprehensive list of currently available kernel privileges may be found in priv.h. New privileges are easily added as required, but the comments on adding privileges found in priv.h and priv(9) should be read before doing so. The new privilege interface exposed sufficient information to the privilege checking routine that it will now be possible for jail to determine whether a particular privilege is granted in the check routine, rather than relying on hints from the calling context via the SUSER_ALLOWJAIL flag. For now, the flag is maintained, but a new jail check function, prison_priv_check(), is exposed from kern_jail.c and used by the privilege check routine to determine if the privilege is permitted in jail. As a result, a centralized list of privileges permitted in jail is now present in kern_jail.c. The MAC Framework is now also able to instrument privilege checks, both to deny privileges otherwise granted (mac_priv_check()), and to grant privileges otherwise denied (mac_priv_grant()), permitting MAC Policy modules to implement privilege models, as well as control a much broader range of system behavior in order to constrain processes running with root privilege. The suser() and suser_cred() functions remain implemented, now in terms of priv_check() and the PRIV_ROOT privilege, for use during the transition and possibly continuing use by third party kernel modules that have not been updated. The PRIV_DRIVER privilege exists to allow device drivers to check privilege without adopting a more specific privilege identifier. This change does not modify the actual security policy, rather, it modifies the interface for privilege checks so changes to the security policy become more feasible. Sponsored by: nCircle Network Security, Inc. Obtained from: TrustedBSD Project Discussed on: arch@ Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri, Alex Lyashkov <umka at sevcity dot net>, Skip Ford <skip dot ford at verizon dot net>, Antoine Brodin <antoine dot brodin at laposte dot net>
2006-11-06 13:37:19 +00:00
priv.9 \
Add prng(9) API Add prng(9) as a replacement for random(9) in the kernel. There are two major differences from random(9) and random(3): - General prng(9) APIs (prng32(9), etc) do not guarantee an implementation or particular sequence; they should not be used for repeatable simulations. - However, specific named API families are also exposed (for now: PCG), and those are expected to be repeatable (when so-guaranteed by the named algorithm). Some minor differences from random(3) and earlier random(9): - PRNG state for the general prng(9) APIs is per-CPU; this eliminates contention on PRNG state in SMP workloads. Each PCPU generator in an SMP system produces a unique sequence. - Better statistical properties than the Park-Miller ("minstd") PRNG (longer period, uniform distribution in all bits, passes BigCrush/PractRand analysis). - Faster than Park-Miller ("minstd") PRNG -- no division is required to step PCG-family PRNGs. For now, random(9) becomes a thin shim around prng32(). Eventually I would like to mechanically switch consumers over to the explicit API. Reviewed by: kib, markj (previous version both) Discussed with: markm Differential Revision: https://reviews.freebsd.org/D25916
2020-08-13 20:48:14 +00:00
prng.9 \
Add helper functions proc_readmem() and proc_writemem(). These helper functions can be used to read in or write a buffer from or to an arbitrary process' address space. Without them, this can only be done using proc_rwmem(), which requires the caller to fill out a uio. This is onerous and results in code duplication; the new functions provide a simpler interface which is sufficient for most existing callers of proc_rwmem(). This change also adds a manual page for proc_rwmem() and the new functions. Reviewed by: jhb, kib Differential Revision: https://reviews.freebsd.org/D4245
2015-12-07 21:33:15 +00:00
proc_rwmem.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pseudofs.9 \
psignal.9 \
Add a pwm subsystem so we can configure pwm controller from kernel and userland. The pwm subsystem consist of API for PWM controllers, pwmbus to register them and a pwm(8) utility to talk to them from userland. Reviewed by: oshgobo (capsicum), bcr (manpage), 0mp (manpage) Differential Revision: https://reviews.freebsd.org/D17938
2018-12-12 20:56:56 +00:00
pwmbus.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
random.9 \
random_harvest.9 \
Add a man page for ratecheck(9) and ppsratecheck(9).
2018-08-17 17:16:38 +00:00
ratecheck.9 \
Add buffer corruption protection (RedZone) for kernel's malloc(9). It detects both: buffer underflows and buffer overflows bugs at runtime (on free(9) and realloc(9)) and prints backtraces from where memory was allocated and from where it was freed. Tested by: kris
2006-01-31 11:09:21 +00:00
redzone.9 \
Add a simple manage for the refcount(9) API. Requested by: rwatson
2009-03-30 18:01:12 +00:00
refcount.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
resettodr.9 \
resource_int_value.9 \
rijndael.9 \
Document the ``resource management'' routines in rman(9). Submitted by: Bruce M. Simpson <bms@spc.org> Reviewed by: mdodd Approved by: des (mentor), re (scottl)
2003-05-16 19:22:27 +00:00
rman.9 \
Hook up rmlock(9) and its links to the build.
2007-11-10 16:47:38 +00:00
rmlock.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rtalloc.9 \
rtentry.9 \
runqueue.9 \
Document read/write locks. Reviewed by: jhb, ru
2006-02-01 19:39:25 +00:00
rwlock.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 \
scheduler.9 \
Add a man page for the SDT_* macros, which can be used to define new static DTrace probes and providers in kernel code. MFC after: 1 week
2013-07-06 20:31:22 +00:00
SDT.9 \
Document kernel functions securelevel_gt and securelevel_ge. Approved by: simon(mentor) Submitted by: Christian S.J. Peron <maneo@bsdpro.com> PR: docs/62331 mdoc(7) cleanup by: ru
2004-03-07 15:22:08 +00:00
securelevel_gt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
selrecord.9 \
sema.9 \
seqc: add man page Reviewed by: markj Earlier version reviewed by: emaste, mjg, bcr, 0mp Differential Revision: https://reviews.freebsd.org/D16744
2019-07-29 21:53:02 +00:00
seqc.9 \
Add a rudimentary man page for sf_bufs, based on my rudimentary understanding of sf_bufs.
2007-01-28 16:07:50 +00:00
sf_buf.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 \
Add a helper API to allow in-kernel code to map portions of shared memory objects created by shm_open(2) into the kernel's address space. This provides a convenient way for creating shared memory buffers between userland and the kernel without requiring custom character devices.
2011-12-14 22:22:19 +00:00
shm_map.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
signal.9 \
sleep.9 \
sleepqueue.9 \
Add a basic man page for the socket(9) kernel programming interface used by the NFS client and server, netsmb, netncp, etc. Reviewed by: ru Fixed by: ru
2006-12-15 23:35:15 +00:00
socket.9 \
Add a man page for stack(9). MFC after: 1 week
2007-11-27 11:02:41 +00:00
stack.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
store.9 \
style.9 \
Create style.lua(9) This covers the lua style guidelines we've generally agreed on so far. It will be revised as work continues and we run into more scenarios that need specified. Discussed with: cem, jilles Differential Revision: https://reviews.freebsd.org/D14423
2018-02-19 01:25:52 +00:00
style.lua.9 \
add superio.4 and superio.9 manual pages This adds basic documentation on what the superio driver is and how other drivers can interact with it. I decided to also document superio's ivar accessors. Reviewed by: bcr, brueffer (both manual contents only) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D21958
2019-10-11 11:13:47 +00:00
${_superio.9} \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
swi.9 \
sx.9 \
Document syscall_helper_register(9), syscall_helper_unregister(9)
2018-02-10 20:34:09 +00:00
syscall_helper_register.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
SYSCALL_MODULE.9 \
Add a basic man page for the sysctl(9) macro interfaces. Previously man pages existed only for the dynamic sysctl interfaces. There's probably more complete and accurate content, better advice, etc, that could be added here. Per scottl's suggest, add a small piece of moralizing text regarding the fact that sysctl names quickly get embedded in system configuration files, libraries, third party applications, and even books, so renaming and removing names after they've been published is a tricky issue. MFC after: 1 month
2006-04-28 10:45:27 +00:00
sysctl.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sysctl_add_oid.9 \
sysctl_ctx_init.9 \
Add a manpage for SYSINIT() and SYSUNINIT(). PR: docs/132884 Submitted by: pluknet, hmp
2010-12-06 15:19:03 +00:00
SYSINIT.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
taskqueue.9 \
Document support for alternate TCP stacks. Differential Revision: https://reviews.freebsd.org/D6940 Reviewed by: hiren Approved by: re (gjb) Sponsored by: Juniper Networks
2016-06-28 13:37:01 +00:00
tcp_functions.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
thread_exit.9 \
time.9 \
tvtohz.9 \
ucred.9 \
uidinfo.9 \
uio.9 \
Rename alloc_unr(9) to unr(9) and adjust the links accordingly. MFC after: 3 weeks
2011-04-27 01:10:15 +00:00
unr.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vaccess.9 \
Add pieces of infrastructure required for NFSv4 ACL support in UFS. Reviewed by: rwatson
2009-09-22 15:15:03 +00:00
vaccess_acl_nfs4.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vaccess_acl_posix1e.9 \
vcount.9 \
Add manpages describing various vfs and vm APIs. Submitted by: Chad David <davidc@acns.ab.ca>
2001-12-02 02:13:35 +00:00
vflush.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VFS.9 \
vfs_busy.9 \
VFS_CHECKEXP.9 \
vfsconf.9 \
VFS_FHTOVP.9 \
vfs_getnewfsid.9 \
Add vfs_getopt.9 to the build, and add links for related functions.
2007-03-02 17:03:56 +00:00
vfs_getopt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vfs_getvfs.9 \
VFS_MOUNT.9 \
Add vfs_mountedfrom.9 to the build.
2008-02-26 21:40:30 +00:00
vfs_mountedfrom.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VFS_QUOTACTL.9 \
VFS_ROOT.9 \
vfs_rootmountalloc.9 \
VFS_SET.9 \
VFS_STATFS.9 \
document vfs_suser.
2004-07-09 22:33:43 +00:00
vfs_suser.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
VFS_SYNC.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vfs_timestamp.9 \
vfs_unbusy.9 \
VFS_UNMOUNT.9 \
vfs_unmountall.9 \
VFS_VGET.9 \
vget.9 \
vgone.9 \
vhold.9 \
vinvalbuf.9 \
Update the pmap(9) documentation to reflect the movement of pmap_prefault() to the machine-independent VM layer, as per alc's recent commit. Add a definition for the new pmap_is_prefaultable() helper function.
2003-10-04 01:30:01 +00:00
vm_fault_prefault.9 \
Add manual pages for the vm_map(9) part of the VM. Reviewed by: juli Approved by: jake (mentor)
2003-09-30 00:56:17 +00:00
vm_map.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vm_map_check_protection.9 \
vm_map_create.9 \
vm_map_delete.9 \
Document the O(log n) algorithm for finding free space. Submitted by: Mark W. Krentel
2004-09-27 04:22:41 +00:00
vm_map_entry_resize_free.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vm_map_find.9 \
vm_map_findspace.9 \
vm_map_inherit.9 \
vm_map_init.9 \
vm_map_insert.9 \
vm_map_lock.9 \
vm_map_lookup.9 \
vm_map_madvise.9 \
vm_map_max.9 \
vm_map_protect.9 \
vm_map_remove.9 \
vm_map_simplify_entry.9 \
vm_map_stack.9 \
vm_map_submap.9 \
vm_map_clean() was long ago renamed to vm_map_sync(). Also, it no longer acquires Giant. MFC after: 1 week
2011-07-09 19:05:28 +00:00
vm_map_sync.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vm_map_wire.9 \
vm_page_alloc.9 \
vm_page_bits.9 \
Hook vm_page_busy.9 to the build
2013-08-26 16:38:40 +00:00
vm_page_busy.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vm_page_deactivate.9 \
vm_page_dontneed.9 \
Document vm_page_aflag_set(9), vm_page_aflag_clear(9) and vm_page_reference(9). Retire vm_page_flag_set() and vm_page_flag_clear() functions. Reviewed by: alc Approved by: re (bz)
2011-09-06 10:40:21 +00:00
vm_page_aflag.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vm_page_free.9 \
vm_page_grab.9 \
vm_page_insert.9 \
vm_page_lookup.9 \
vm_page_rename.9 \
vm_page_wire.9 \
vm_set_page_size.9 \
Add manual page for vmem(9). Obtained from NetBSD, modified to match our implementation. Obtained from: NetBSD
2013-07-12 14:25:58 +00:00
vmem.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vn_fullpath.9 \
vn_isdisk.9 \
MFp4: @179066 Add page which describes VNET network stack virtualization infrastructure. Submitted by: bz Sponsored by: The FreeBSD Foundation Sponsored by: CK Software GmbH
2014-11-20 09:56:34 +00:00
vnet.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vnode.9 \
VOP_ACCESS.9 \
VOP_ACLCHECK.9 \
Add manpages for VOP_ADVISE() and VOP_ALLOCATE(). Approved by: re (gjb)
2013-10-07 20:30:05 +00:00
VOP_ADVISE.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VOP_ADVLOCK.9 \
Add manpages for VOP_ADVISE() and VOP_ALLOCATE(). Approved by: re (gjb)
2013-10-07 20:30:05 +00:00
VOP_ALLOCATE.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VOP_ATTRIB.9 \
Add a VOP_BMAP(9) man page Reviewed by: mckusick MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D20704
2019-06-20 13:59:46 +00:00
VOP_BMAP.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VOP_BWRITE.9 \
Create a man page for VOP_COPY_FILE_RANGE(9). r350315 created a Linux compatible copy_file_range(2) syscall. It uses a VOP method called VOP_COPY_FILE_RANGE so that file systems, such as the NFSv4.2 client can do file system specific copying. For NFSv4.2, this allows the copying to be done locally on the NFS server, avoiding transferring the data across the wire twice. This is a new man page (content changed). Reviewed by: kib, asomers Relnotes: yes Differential Revision: https://reviews.freebsd.org/D20584
2019-07-25 06:20:00 +00:00
VOP_COPY_FILE_RANGE.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
VOP_CREATE.9 \
VOP_FSYNC.9 \
VOP_GETACL.9 \
VOP_GETEXTATTR.9 \
VOP_GETPAGES.9 \
VOP_INACTIVE.9 \
VOP_IOCTL.9 \
VOP_LINK.9 \
VOP_LISTEXTATTR.9 \
VOP_LOCK.9 \
VOP_LOOKUP.9 \
VOP_OPENCLOSE.9 \
VOP_PATHCONF.9 \
VOP_PRINT.9 \
VOP_RDWR.9 \
VOP_READDIR.9 \
VOP_READLINK.9 \
VOP_REALLOCBLKS.9 \
VOP_REMOVE.9 \
VOP_RENAME.9 \
VOP_REVOKE.9 \
VOP_SETACL.9 \
VOP_SETEXTATTR.9 \
VOP_STRATEGY.9 \
Add a man page for VOP_VPTOCNP. Reviewed by: arch Approved by: kib
2008-12-12 01:08:28 +00:00
VOP_VPTOCNP.9 \
VFS_VPTOFH(9) was replaced with VOP_VPTOFH(9). VFS_VPTOFH.9 was repo-copied to VOP_VPTOFH.9. Repo-copy done by: joe
2007-02-16 14:27:59 +00:00
VOP_VPTOFH.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vref.9 \
Add vrefcnt.9 to the build.
2008-02-26 20:10:32 +00:00
vrefcnt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
vrele.9 \
Sort MAN= section.
2001-07-10 07:42:35 +00:00
vslock.9 \
Add contents to manualpage for generic watchdog facility. Formatting likely to break several UN resolutions.
2004-02-28 20:08:41 +00:00
watchdog.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
zone.9
Install: cdevsw_add.9 cdevsw_remove.9 devsw.9 major.9 minor.9 umajor.9 uminor.9 vn_isdisk.9
2001-07-10 07:28:11 +00:00
Rename alloc_unr(9) to unr(9) and adjust the links accordingly. MFC after: 3 weeks
2011-04-27 01:10:15 +00:00
MLINKS= unr.9 alloc_unr.9 \
unr.9 alloc_unrl.9 \
unr.9 alloc_unr_specific.9 \
Add clearing function for unr(9). Previously before you could call unrhdr_delete you needed to individually free every allocated unit. It is useful to be able to tear down the unr without having to go through this process, as it is significantly faster than freeing the individual units. Reviewed by: cem, lidl Approved by: rstone (mentor) Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D12591
2017-10-11 21:53:50 +00:00
unr.9 clear_unrhdr.9 \
Rename alloc_unr(9) to unr(9) and adjust the links accordingly. MFC after: 3 weeks
2011-04-27 01:10:15 +00:00
unr.9 delete_unrhdr.9 \
unr.9 free_unr.9 \
unr.9 new_unrhdr.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=accept_filter.9 accept_filt_add.9 \
accept_filter.9 accept_filt_del.9 \
accept_filter.9 accept_filt_generic_mod_event.9 \
accept_filter.9 accept_filt_get.9
Manpage for unit allocator functions. Reviewed by: phk
2005-04-20 19:11:05 +00:00
MLINKS+=alq.9 ALQ.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
alq.9 alq_close.9 \
alq.9 alq_flush.9 \
alq.9 alq_get.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
alq.9 alq_getn.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
alq.9 alq_open.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
alq.9 alq_open_flags.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
alq.9 alq_post.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
alq.9 alq_post_flags.9 \
alq.9 alq_write.9 \
alq.9 alq_writen.9
Add altq(9) explaining about the IFQ_* and IFQ_DRV_* macros in if_var.h and how to convert drivers. Obtained from: NetBSD (with changes) Reviewed by: josef
2004-08-07 12:35:56 +00:00
MLINKS+=altq.9 ALTQ.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=atomic.9 atomic_add.9 \
atomic.9 atomic_clear.9 \
atomic.9 atomic_cmpset.9 \
Add missing MLINK. MFC after: 3 days
2018-06-26 09:30:14 +00:00
atomic.9 atomic_fcmpset.9 \
- Document atomic_fetchadd(9) and add a MLINK. - Add arm and ppc to the list of archs not supporting operations on 64-bit integers. - Update the sample code for acquiring a mutex to be more recent and to take into account the recent atomic_foo_ptr() changes. MFC after: 1 week
2005-09-27 17:59:29 +00:00
atomic.9 atomic_fetchadd.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
atomic.9 atomic_load.9 \
atomic.9 atomic_readandclear.9 \
atomic.9 atomic_set.9 \
atomic.9 atomic_store.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
atomic.9 atomic_subtract.9 \
atomic.9 atomic_swap.9 \
atomic.9: Add missing MLINK for testandclear, thread_fence routines Missed in r299912, r326982. X-MFC-With: r299912, r326982 Sponsored by: Dell EMC Isilon
2018-06-26 16:20:19 +00:00
atomic.9 atomic_testandclear.9 \
atomic.9 atomic_testandset.9 \
atomic.9 atomic_thread_fence.9
bhnd(4) update inline documentation comments and man pages. This includes a number of copyedits for the inline code documentation comments, updates to the existing bhnd(4), bhndb(4), bcma(4), and siba(4) man pages, and new man pages for bhnd_chipc(4), bhnd_pmu(4), bhndb_pci(4), bhnd(9), and bhnd_erom(9). Approved by: adrian (mentor) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D13021
2017-11-27 21:30:49 +00:00
MLINKS+=bhnd.9 BHND_MATCH_BOARD_TYPE.9 \
bhnd.9 BHND_MATCH_BOARD_VENDOR.9 \
bhnd.9 BHND_MATCH_CHIP_ID.9 \
bhnd.9 BHND_MATCH_CHIP_PKG.9 \
bhnd.9 BHND_MATCH_CHIP_REV.9 \
bhnd.9 BHND_MATCH_CORE_ID.9 \
bhnd.9 BHND_MATCH_CORE_VENDOR.9 \
bhnd.9 bhnd_activate_resource.9 \
bhnd.9 bhnd_alloc_pmu.9 \
bhnd.9 bhnd_alloc_resource.9 \
bhnd.9 bhnd_alloc_resource_any.9 \
bhnd.9 bhnd_alloc_resources.9 \
bhnd.9 bhnd_board_matches.9 \
bhnd.9 bhnd_bus_match_child.9 \
bhnd.9 bhnd_bus_read_1.9 \
bhnd.9 bhnd_bus_read_2.9 \
bhnd.9 bhnd_bus_read_4.9 \
bhnd.9 bhnd_bus_read_stream_1.9 \
bhnd.9 bhnd_bus_read_stream_2.9 \
bhnd.9 bhnd_bus_read_stream_4.9 \
bhnd.9 bhnd_bus_write_1.9 \
bhnd.9 bhnd_bus_write_2.9 \
bhnd.9 bhnd_bus_write_4.9 \
bhnd.9 bhnd_bus_write_stream_1.9 \
bhnd.9 bhnd_bus_write_stream_2.9 \
bhnd.9 bhnd_bus_write_stream_4.9 \
bhnd.9 bhnd_chip_matches.9 \
bhnd.9 bhnd_core_class.9 \
bhnd.9 bhnd_core_get_match_desc.9 \
bhnd.9 bhnd_core_matches.9 \
bhnd.9 bhnd_core_name.9 \
bhnd.9 bhnd_cores_equal.9 \
bhnd.9 bhnd_deactivate_resource.9 \
bhnd.9 bhnd_decode_port_rid.9 \
bhnd.9 bhnd_deregister_provider.9 \
bhnd.9 bhnd_device_lookup.9 \
bhnd.9 bhnd_device_matches.9 \
bhnd.9 bhnd_device_quirks.9 \
bhnd.9 bhnd_driver_get_erom_class.9 \
bhnd.9 bhnd_enable_clocks.9 \
bhnd.9 bhnd_find_core_class.9 \
bhnd.9 bhnd_find_core_name.9 \
bhnd.9 bhnd_format_chip_id.9 \
bhnd.9 bhnd_get_attach_type.9 \
bhnd.9 bhnd_get_chipid.9 \
bhnd.9 bhnd_get_class.9 \
bhnd.9 bhnd_get_clock_freq.9 \
bhnd.9 bhnd_get_clock_latency.9 \
bhnd.9 bhnd_get_core_index.9 \
bhnd.9 bhnd_get_core_info.9 \
bhnd.9 bhnd_get_core_unit.9 \
bhnd.9 bhnd_get_device.9 \
bhnd.9 bhnd_get_device_name.9 \
bhnd.9 bhnd_get_dma_translation.9 \
bhnd.9 bhnd_get_hwrev.9 \
bhnd.9 bhnd_get_intr_count.9 \
bhnd.9 bhnd_get_intr_ivec.9 \
bhnd.9 bhnd_get_port_count.9 \
bhnd.9 bhnd_get_port_rid.9 \
bhnd.9 bhnd_get_region_addr.9 \
bhnd.9 bhnd_get_region_count.9 \
bhnd.9 bhnd_get_vendor.9 \
bhnd.9 bhnd_get_vendor_name.9 \
bhnd.9 bhnd_hwrev_matches.9 \
bhnd.9 bhnd_is_hw_suspended.9 \
bhnd.9 bhnd_is_region_valid.9 \
bhnd.9 bhnd_map_intr.9 \
bhnd.9 bhnd_match_core.9 \
bhnd.9 bhnd_nvram_getvar.9 \
bhnd.9 bhnd_nvram_getvar_array.9 \
bhnd.9 bhnd_nvram_getvar_int.9 \
bhnd.9 bhnd_nvram_getvar_int16.9 \
bhnd.9 bhnd_nvram_getvar_int32.9 \
bhnd.9 bhnd_nvram_getvar_int8.9 \
bhnd.9 bhnd_nvram_getvar_str.9 \
bhnd.9 bhnd_nvram_getvar_uint.9 \
bhnd.9 bhnd_nvram_getvar_uint16.9 \
bhnd.9 bhnd_nvram_getvar_uint32.9 \
bhnd.9 bhnd_nvram_getvar_uint8.9 \
bhnd.9 bhnd_nvram_string_array_next.9 \
bhnd.9 bhnd_read_board_info.9 \
bhnd.9 bhnd_read_config.9 \
bhnd.9 bhnd_read_ioctl.9 \
bhnd.9 bhnd_read_iost.9 \
bhnd.9 bhnd_register_provider.9 \
bhnd.9 bhnd_release_ext_rsrc.9 \
bhnd.9 bhnd_release_pmu.9 \
bhnd.9 bhnd_release_provider.9 \
bhnd.9 bhnd_release_resource.9 \
bhnd.9 bhnd_release_resources.9 \
bhnd.9 bhnd_request_clock.9 \
bhnd.9 bhnd_request_ext_rsrc.9 \
bhnd.9 bhnd_reset_hw.9 \
bhnd.9 bhnd_retain_provider.9 \
bhnd.9 bhnd_set_custom_core_desc.9 \
bhnd.9 bhnd_set_default_core_desc.9 \
bhnd.9 bhnd_suspend_hw.9 \
bhnd.9 bhnd_unmap_intr.9 \
bhnd.9 bhnd_vendor_name.9 \
bhnd.9 bhnd_write_config.9 \
bhnd.9 bhnd_write_ioctl.9
MLINKS+=bhnd_erom.9 bhnd_erom_alloc.9 \
bhnd_erom.9 bhnd_erom_dump.9 \
bhnd_erom.9 bhnd_erom_fini_static.9 \
bhnd_erom.9 bhnd_erom_free.9 \
bhnd_erom.9 bhnd_erom_free_core_table.9 \
bhnd_erom.9 bhnd_erom_get_core_table.9 \
bhnd_erom.9 bhnd_erom_init_static.9 \
bhnd_erom.9 bhnd_erom_io.9 \
bhnd_erom.9 bhnd_erom_io_fini.9 \
bhnd_erom.9 bhnd_erom_io_map.9 \
bhnd_erom.9 bhnd_erom_io_read.9 \
bhnd_erom.9 bhnd_erom_iobus_init.9 \
bhnd_erom.9 bhnd_erom_iores_new.9 \
bhnd_erom.9 bhnd_erom_lookup_core.9 \
bhnd_erom.9 bhnd_erom_lookup_core_addr.9 \
bhnd_erom.9 bhnd_erom_probe.9 \
bhnd_erom.9 bhnd_erom_probe_driver_classes.9
Document bitset(9)
2015-10-17 19:55:58 +00:00
MLINKS+=bitset.9 BITSET_DEFINE.9 \
bitset.9 BITSET_T_INITIALIZER.9 \
bitset.9 BITSET_FSET.9 \
bitset.9 BIT_CLR.9 \
bitset.9 BIT_COPY.9 \
bitset.9 BIT_ISSET.9 \
bitset.9 BIT_SET.9 \
bitset.9 BIT_ZERO.9 \
bitset.9 BIT_FILL.9 \
bitset.9 BIT_SETOF.9 \
bitset.9 BIT_EMPTY.9 \
bitset.9 BIT_ISFULLSET.9 \
bitset.9 BIT_FFS.9 \
Add missing bitset(9) MLINKS. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D25713
2020-07-19 12:22:32 +00:00
bitset.9 BIT_FLS.9 \
Document bitset(9)
2015-10-17 19:55:58 +00:00
bitset.9 BIT_COUNT.9 \
bitset.9 BIT_SUBSET.9 \
bitset.9 BIT_OVERLAP.9 \
bitset.9 BIT_CMP.9 \
bitset.9 BIT_OR.9 \
Add missing bitset(9) MLINKS. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D25713
2020-07-19 12:22:32 +00:00
bitset.9 BIT_OR2.9 \
Document bitset(9)
2015-10-17 19:55:58 +00:00
bitset.9 BIT_AND.9 \
Add missing bitset(9) MLINKS. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D25713
2020-07-19 12:22:32 +00:00
bitset.9 BIT_AND2.9 \
bitset: rename confusing macro NAND to ANDNOT s/BIT_NAND/BIT_ANDNOT/, and for CPU and DOMAINSET too. The actual implementation is "and not" (or "but not"), i.e. A but not B. Fortunately this does appear to be what all existing callers want. Don't supply a NAND (not (A and B)) operation at this time. Discussed with: jeff Reviewed by: cem Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D22791
2019-12-13 09:32:16 +00:00
bitset.9 BIT_ANDNOT.9 \
Add missing bitset(9) MLINKS. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D25713
2020-07-19 12:22:32 +00:00
bitset.9 BIT_ANDNOT2.9 \
bitset.9 BIT_XOR.9 \
bitset.9 BIT_XOR2.9 \
Document bitset(9)
2015-10-17 19:55:58 +00:00
bitset.9 BIT_CLR_ATOMIC.9 \
bitset.9 BIT_SET_ATOMIC.9 \
bitset.9 BIT_SET_ATOMIC_ACQ.9 \
bitset.9 BIT_AND_ATOMIC.9 \
bitset.9 BIT_OR_ATOMIC.9 \
bitset.9 BIT_COPY_STORE_REL.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=bpf.9 bpfattach.9 \
bpf.9 bpfattach2.9 \
bpf.9 bpfdetach.9 \
bpf.9 bpf_filter.9 \
Add links to all bpf(9) functions.
2008-08-28 17:04:52 +00:00
bpf.9 bpf_mtap.9 \
bpf.9 bpf_mtap2.9 \
bpf.9 bpf_tap.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
bpf.9 bpf_validate.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=buf.9 bp.9
Manpages for the buf_ring and drbr interfaces. Submitted by: kmacy (aeons ago) MFC after: 1 week
2012-01-30 21:02:25 +00:00
MLINKS+=buf_ring.9 buf_ring_alloc.9 \
buf_ring.9 buf_ring_free.9 \
buf_ring.9 buf_ring_enqueue.9 \
buf_ring.9 buf_ring_enqueue_bytes.9 \
buf_ring.9 buf_ring_dequeue_mc.9 \
buf_ring.9 buf_ring_dequeue_sc.9 \
buf_ring.9 buf_ring_count.9 \
buf_ring.9 buf_ring_empty.9 \
buf_ring.9 buf_ring_full.9 \
buf_ring.9 buf_ring_peek.9
Add a new man page for bus_activate_resource and bus_deactivate_resource. It could use some improvement, and others are welcomed to do so :-)
2003-03-29 05:16:15 +00:00
MLINKS+=bus_activate_resource.9 bus_deactivate_resource.9
Add bus_alloc_resource_any(9), which does bus_alloc_resource() with the appropriate default values. Document it in the manpage. Submitted by: Mark Santcroos <marks@ripe.net> Reviewed by: imp, dfr, bde Abstains: bde
2004-03-17 17:40:34 +00:00
MLINKS+=bus_alloc_resource.9 bus_alloc_resource_any.9
Add a manual page for BUS_BIND_INTR() and bus_bind_intr(). MFC after: 1 week
2009-10-14 15:58:59 +00:00
MLINKS+=BUS_BIND_INTR.9 bus_bind_intr.9
Add a facility for associating optional descriptions with active interrupt handlers. This is primarily intended as a way to allow devices that use multiple interrupts (e.g. MSI) to meaningfully distinguish the various interrupt handlers. - Add a new BUS_DESCRIBE_INTR() method to the bus interface to associate a description with an active interrupt handler setup by BUS_SETUP_INTR. It has a default method (bus_generic_describe_intr()) which simply passes the request up to the parent device. - Add a bus_describe_intr() wrapper around BUS_DESCRIBE_INTR() that supports printf(9) style formatting using var args. - Reserve MAXCOMLEN bytes in the intr_handler structure to hold the name of an interrupt handler and copy the name passed to intr_event_add_handler() into that buffer instead of just saving the pointer to the name. - Add a new intr_event_describe_handler() which appends a description string to an interrupt handler's name. - Implement support for interrupt descriptions on amd64 and i386 by having the nexus(4) driver supply a custom bus_describe_intr method that invokes a new intr_describe() MD routine which in turn looks up the associated interrupt event and invokes intr_event_describe_handler(). Requested by: many Reviewed by: scottl MFC after: 2 weeks
2009-10-15 14:54:35 +00:00
MLINKS+=BUS_DESCRIBE_INTR.9 bus_describe_intr.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=bus_dma.9 busdma.9 \
bus_dma.9 bus_dmamap_create.9 \
bus_dma.9 bus_dmamap_destroy.9 \
bus_dma.9 bus_dmamap_load.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
bus_dma.9 bus_dmamap_load_bio.9 \
bus_dma.9 bus_dmamap_load_ccb.9 \
Add support for optional separate output buffers to in-kernel crypto. Some crypto consumers such as GELI and KTLS for file-backed sendfile need to store their output in a separate buffer from the input. Currently these consumers copy the contents of the input buffer into the output buffer and queue an in-place crypto operation on the output buffer. Using a separate output buffer avoids this copy. - Create a new 'struct crypto_buffer' describing a crypto buffer containing a type and type-specific fields. crp_ilen is gone, instead buffers that use a flat kernel buffer have a cb_buf_len field for their length. The length of other buffer types is inferred from the backing store (e.g. uio_resid for a uio). Requests now have two such structures: crp_buf for the input buffer, and crp_obuf for the output buffer. - Consumers now use helper functions (crypto_use_*, e.g. crypto_use_mbuf()) to configure the input buffer. If an output buffer is not configured, the request still modifies the input buffer in-place. A consumer uses a second set of helper functions (crypto_use_output_*) to configure an output buffer. - Consumers must request support for separate output buffers when creating a crypto session via the CSP_F_SEPARATE_OUTPUT flag and are only permitted to queue a request with a separate output buffer on sessions with this flag set. Existing drivers already reject sessions with unknown flags, so this permits drivers to be modified to support this extension without requiring all drivers to change. - Several data-related functions now have matching versions that operate on an explicit buffer (e.g. crypto_apply_buf, crypto_contiguous_subsegment_buf, bus_dma_load_crp_buf). - Most of the existing data-related functions operate on the input buffer. However crypto_copyback always writes to the output buffer if a request uses a separate output buffer. - For the regions in input/output buffers, the following conventions are followed: - AAD and IV are always present in input only and their fields are offsets into the input buffer. - payload is always present in both buffers. If a request uses a separate output buffer, it must set a new crp_payload_start_output field to the offset of the payload in the output buffer. - digest is in the input buffer for verify operations, and in the output buffer for compute operations. crp_digest_start is relative to the appropriate buffer. - Add a crypto buffer cursor abstraction. This is a more general form of some bits in the cryptosoft driver that tried to always use uio's. However, compared to the original code, this avoids rewalking the uio iovec array for requests with multiple vectors. It also avoids allocate an iovec array for mbufs and populating it by instead walking the mbuf chain directly. - Update the cryptosoft(4) driver to support separate output buffers making use of the cursor abstraction. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24545
2020-05-25 22:12:04 +00:00
bus_dma.9 bus_dmamap_load_crp.9 \
bus_dma.9 bus_dmamap_load_crp_buffer.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_dma.9 bus_dmamap_load_mbuf.9 \
MLINK for bus_dmamap_load_mbuf_sg(9)
2007-02-12 17:53:21 +00:00
bus_dma.9 bus_dmamap_load_mbuf_sg.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
bus_dma.9 bus_dmamap_load_uio.9 \
bus_dma.9 bus_dmamap_sync.9 \
bus_dma.9 bus_dmamap_unload.9 \
bus_dma.9 bus_dmamem_alloc.9 \
bus_dma.9 bus_dmamem_free.9 \
bus_dma.9 bus_dma_tag_create.9 \
bus_dma.9 bus_dma_tag_destroy.9
MLINKS+=bus_generic_read_ivar.9 bus_generic_write_ivar.9
Add a new bus method to fetch device-specific CPU sets. bus_get_cpus() returns a specified set of CPUs for a device. It accepts an enum for the second parameter that indicates the type of cpuset to request. Currently two valus are supported: - LOCAL_CPUS (on x86 this returns all the CPUs in the package closest to the device when DEVICE_NUMA is enabled) - INTR_CPUS (like LOCAL_CPUS but only returns 1 SMT thread for each core) For systems that do not support NUMA (or if it is not enabled in the kernel config), LOCAL_CPUS fails with EINVAL. INTR_CPUS is mapped to 'all_cpus' by default. The idea is that INTR_CPUS should always return a valid set. Device drivers which want to use per-CPU interrupts should start using INTR_CPUS instead of simply assigning interrupts to all available CPUs. In the future we may wish to add tunables to control the policy of INTR_CPUS (e.g. should it be local-only or global, should it ignore SMT threads or not). The x86 nexus driver exposes the internal set of interrupt CPUs from the the x86 interrupt code via INTR_CPUS. The ACPI bus driver and PCI bridge drivers use _PXM to return a suitable LOCAL_CPUS set when _PXM exists and DEVICE_NUMA is enabled. They also and the global INTR_CPUS set from the nexus driver with the per-domain set from _PXM to generate a local INTR_CPUS set for child devices. Compared to the r298933, this version uses 'struct _cpuset' in <sys/bus.h> instead of 'cpuset_t' to avoid requiring <sys/param.h> (<sys/_cpuset.h> still requires <sys/param.h> for MAXCPU even though <sys/_bitset.h> does not after recent changes).
2016-05-09 20:50:21 +00:00
MLINKS+=BUS_GET_CPUS.9 bus_get_cpus.9
Add new bus methods for mapping resources. Add a pair of bus methods that can be used to "map" resources for direct CPU access using bus_space(9). bus_map_resource() creates a mapping and bus_unmap_resource() releases a previously created mapping. Mappings are described by 'struct resource_map' object. Pointers to these objects can be passed as the first argument to the bus_space wrapper API used for bus resources. Drivers that wish to map all of a resource using default settings (for example, using uncacheable memory attributes) do not need to change. However, drivers that wish to use non-default settings can now do so without jumping through hoops. First, an RF_UNMAPPED flag is added to request that a resource is not implicitly mapped with the default settings when it is activated. This permits other activation steps (such as enabling I/O or memory decoding in a device's PCI command register) to be taken without creating a mapping. Right now the AGP drivers don't set RF_ACTIVE to avoid using up a large amount of KVA to map the AGP aperture on 32-bit platforms. Once RF_UNMAPPED is supported on all platforms that support AGP this can be changed to using RF_UNMAPPED with RF_ACTIVE instead. Second, bus_map_resource accepts an optional structure that defines additional settings for a given mapping. For example, a driver can now request to map only a subset of a resource instead of the entire range. The AGP driver could also use this to only map the first page of the aperture (IIRC, it calls pmap_mapdev() directly to map the first page currently). I will also eventually change the PCI-PCI bridge driver to request mappings of the subset of the I/O window resource on its parent side to create mappings for child devices rather than passing child resources directly up to nexus to be mapped. This also permits bridges that do address translation to request suitable mappings from a resource on the "upper" side of the bus when mapping resources on the "lower" side of the bus. Another attribute that can be specified is an alternate memory attribute for memory-mapped resources. This can be used to request a Write-Combining mapping of a PCI BAR in an MI fashion. (Currently the drivers that do this call pmap_change_attr() directly for x86 only.) Note that this commit only adds the MI framework. Each platform needs to add support for handling RF_UNMAPPED and thew new bus_map/unmap_resource methods. Generally speaking, any drivers that are calling rman_set_bustag() and rman_set_bushandle() need to be updated. Discussed on: arch Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D5237
2016-05-20 17:57:47 +00:00
MLINKS+=bus_map_resource.9 bus_unmap_resource.9 \
bus_map_resource.9 resource_init_map_request.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=BUS_READ_IVAR.9 BUS_WRITE_IVAR.9
MLINKS+=BUS_SETUP_INTR.9 bus_setup_intr.9 \
BUS_SETUP_INTR.9 BUS_TEARDOWN_INTR.9 \
BUS_SETUP_INTR.9 bus_teardown_intr.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=bus_space.9 bus_space_alloc.9 \
bus_space.9 bus_space_barrier.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_copy_region_1.9 \
bus_space.9 bus_space_copy_region_2.9 \
bus_space.9 bus_space_copy_region_4.9 \
bus_space.9 bus_space_copy_region_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_copy_region_stream_1.9 \
bus_space.9 bus_space_copy_region_stream_2.9 \
bus_space.9 bus_space_copy_region_stream_4.9 \
bus_space.9 bus_space_copy_region_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_free.9 \
bus_space.9 bus_space_map.9 \
bus_space.9 bus_space_read_1.9 \
bus_space.9 bus_space_read_2.9 \
bus_space.9 bus_space_read_4.9 \
bus_space.9 bus_space_read_8.9 \
bus_space.9 bus_space_read_multi_1.9 \
bus_space.9 bus_space_read_multi_2.9 \
bus_space.9 bus_space_read_multi_4.9 \
bus_space.9 bus_space_read_multi_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_read_multi_stream_1.9 \
bus_space.9 bus_space_read_multi_stream_2.9 \
bus_space.9 bus_space_read_multi_stream_4.9 \
bus_space.9 bus_space_read_multi_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_read_region_1.9 \
bus_space.9 bus_space_read_region_2.9 \
bus_space.9 bus_space_read_region_4.9 \
bus_space.9 bus_space_read_region_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_read_region_stream_1.9 \
bus_space.9 bus_space_read_region_stream_2.9 \
bus_space.9 bus_space_read_region_stream_4.9 \
bus_space.9 bus_space_read_region_stream_8.9 \
Sort MAN and MLINKS lists.
2006-10-05 12:40:44 +00:00
bus_space.9 bus_space_read_stream_1.9 \
bus_space.9 bus_space_read_stream_2.9 \
bus_space.9 bus_space_read_stream_4.9 \
bus_space.9 bus_space_read_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_set_multi_1.9 \
bus_space.9 bus_space_set_multi_2.9 \
bus_space.9 bus_space_set_multi_4.9 \
bus_space.9 bus_space_set_multi_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_set_multi_stream_1.9 \
bus_space.9 bus_space_set_multi_stream_2.9 \
bus_space.9 bus_space_set_multi_stream_4.9 \
bus_space.9 bus_space_set_multi_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_set_region_1.9 \
bus_space.9 bus_space_set_region_2.9 \
bus_space.9 bus_space_set_region_4.9 \
bus_space.9 bus_space_set_region_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_set_region_stream_1.9 \
bus_space.9 bus_space_set_region_stream_2.9 \
bus_space.9 bus_space_set_region_stream_4.9 \
bus_space.9 bus_space_set_region_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_subregion.9 \
bus_space.9 bus_space_unmap.9 \
bus_space.9 bus_space_write_1.9 \
bus_space.9 bus_space_write_2.9 \
bus_space.9 bus_space_write_4.9 \
bus_space.9 bus_space_write_8.9 \
bus_space.9 bus_space_write_multi_1.9 \
bus_space.9 bus_space_write_multi_2.9 \
bus_space.9 bus_space_write_multi_4.9 \
bus_space.9 bus_space_write_multi_8.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_write_multi_stream_1.9 \
bus_space.9 bus_space_write_multi_stream_2.9 \
bus_space.9 bus_space_write_multi_stream_4.9 \
bus_space.9 bus_space_write_multi_stream_8.9 \
add links for the functions documented in bus_space.9...
2006-04-04 22:56:08 +00:00
bus_space.9 bus_space_write_region_1.9 \
bus_space.9 bus_space_write_region_2.9 \
bus_space.9 bus_space_write_region_4.9 \
document the various bus_space_*_stream_? functions...
2006-04-22 03:58:41 +00:00
bus_space.9 bus_space_write_region_8.9 \
bus_space.9 bus_space_write_region_stream_1.9 \
bus_space.9 bus_space_write_region_stream_2.9 \
bus_space.9 bus_space_write_region_stream_4.9 \
Sort MAN and MLINKS lists.
2006-10-05 12:40:44 +00:00
bus_space.9 bus_space_write_region_stream_8.9 \
bus_space.9 bus_space_write_stream_1.9 \
bus_space.9 bus_space_write_stream_2.9 \
bus_space.9 bus_space_write_stream_4.9 \
bus_space.9 bus_space_write_stream_8.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=byteorder.9 be16dec.9 \
byteorder.9 be16enc.9 \
byteorder.9 be16toh.9 \
byteorder.9 be32dec.9 \
byteorder.9 be32enc.9 \
byteorder.9 be32toh.9 \
byteorder.9 be64dec.9 \
byteorder.9 be64enc.9 \
byteorder.9 be64toh.9 \
byteorder.9 bswap16.9 \
byteorder.9 bswap32.9 \
byteorder.9 bswap64.9 \
byteorder.9 htobe16.9 \
byteorder.9 htobe32.9 \
byteorder.9 htobe64.9 \
byteorder.9 htole16.9 \
byteorder.9 htole32.9 \
byteorder.9 htole64.9 \
byteorder.9 le16dec.9 \
byteorder.9 le16enc.9 \
byteorder.9 le16toh.9 \
byteorder.9 le32dec.9 \
byteorder.9 le32enc.9 \
byteorder.9 le32toh.9 \
byteorder.9 le64dec.9 \
byteorder.9 le64enc.9 \
byteorder.9 le64toh.9
Remove the deprecated timeout(9) interface. All in-tree consumers have been converted to callout(9). Reviewed by: kib, markj Differential Revision: https://reviews.freebsd.org/D22602
2019-12-13 21:03:12 +00:00
MLINKS+=callout.9 callout_active.9 \
callout.9 callout_async_drain.9 \
callout.9 callout_deactivate.9 \
callout.9 callout_drain.9 \
callout.9 callout_init.9 \
callout.9 callout_init_mtx.9 \
callout.9 callout_init_rm.9 \
callout.9 callout_init_rw.9 \
callout.9 callout_pending.9 \
callout.9 callout_reset.9 \
callout.9 callout_reset_curcpu.9 \
callout.9 callout_reset_on.9 \
callout.9 callout_reset_sbt.9 \
callout.9 callout_reset_sbt_curcpu.9 \
callout.9 callout_reset_sbt_on.9 \
callout.9 callout_schedule.9 \
callout.9 callout_schedule_curcpu.9 \
callout.9 callout_schedule_on.9 \
callout.9 callout_schedule_sbt.9 \
callout.9 callout_schedule_sbt_curcpu.9 \
callout.9 callout_schedule_sbt_on.9 \
callout.9 callout_stop.9 \
callout.9 callout_when.9
Introduce cnv man page. Submitted by: Adam Starak <starak.adam@gmail.com> Reviewed by: cem@, wblock@ Differential Revision: https://reviews.freebsd.org/D7249
2016-08-27 13:47:52 +00:00
MLINKS+=cnv.9 cnvlist.9 \
cnv.9 cnvlist_free_binary.9 \
cnv.9 cnvlist_free_bool.9 \
cnv.9 cnvlist_free_bool_array.9 \
cnv.9 cnvlist_free_descriptor.9 \
cnv.9 cnvlist_free_descriptor_array.9 \
cnv.9 cnvlist_free_null.9 \
cnv.9 cnvlist_free_number.9 \
cnv.9 cnvlist_free_number_array.9 \
cnv.9 cnvlist_free_nvlist.9 \
cnv.9 cnvlist_free_nvlist_array.9 \
cnv.9 cnvlist_free_string.9 \
cnv.9 cnvlist_free_string_array.9 \
cnv.9 cnvlist_get_binary.9 \
cnv.9 cnvlist_get_bool.9 \
cnv.9 cnvlist_get_bool_array.9 \
cnv.9 cnvlist_get_descriptor.9 \
cnv.9 cnvlist_get_descriptor_array.9 \
cnv.9 cnvlist_get_number.9 \
cnv.9 cnvlist_get_number_array.9 \
cnv.9 cnvlist_get_nvlist.9 \
cnv.9 cnvlist_get_nvlist_array.9 \
cnv.9 cnvlist_get_string.9 \
cnv.9 cnvlist_get_string_array.9 \
cnv.9 cnvlist_take_binary.9 \
cnv.9 cnvlist_take_bool.9 \
cnv.9 cnvlist_take_bool_array.9 \
cnv.9 cnvlist_take_descriptor.9 \
cnv.9 cnvlist_take_descriptor_array.9 \
cnv.9 cnvlist_take_number.9 \
cnv.9 cnvlist_take_number_array.9 \
cnv.9 cnvlist_take_nvlist.9 \
cnv.9 cnvlist_take_nvlist_array.9 \
cnv.9 cnvlist_take_string.9 \
cnv.9 cnvlist_take_string_array.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=condvar.9 cv_broadcast.9 \
- Document cv_broadcastpri(). - Remove references to cv_waitq_*() as they no longer exist.
2004-03-10 15:57:25 +00:00
condvar.9 cv_broadcastpri.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
condvar.9 cv_destroy.9 \
condvar.9 cv_init.9 \
condvar.9 cv_signal.9 \
condvar.9 cv_timedwait.9 \
condvar.9 cv_timedwait_sig.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
condvar.9 cv_timedwait_sig_sbt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
condvar.9 cv_wait.9 \
condvar.9 cv_wait_sig.9 \
- Document cv_wait_unlock(9). - Don't claim that the mutex is atomically reacquired when a cv_wait routine returns. There's nothing atomic or magical about the lock reacquire. The only magic is that we atomically drop the lock by placing the thread on the sleep queue before dropping the lock.
2007-03-09 16:59:27 +00:00
condvar.9 cv_wait_unlock.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
condvar.9 cv_wmesg.9
Document config_intrhook. MFC After: 250 millifortnights
2006-09-25 20:12:13 +00:00
MLINKS+=config_intrhook.9 config_intrhook_disestablish.9 \
Add config_intrhook_oneshot(): schedule an intrhook function and unregister it automatically after it runs. The config_intrhook mechanism allows a driver to stall the boot process until device(s) required for booting are available, by not allowing system inits to proceed until all intrhook functions have been unregistered. Virtually all existing code simply unregisters from within the hook function when it gets called. This new function makes that common usage more convenient. Instead of allocating and filling in a struct, passing it to a function that might (in theory) fail, and checking the return code, now a driver can simply call this cannot-fail routine, passing just the intrhook function and its arg. Differential Revision: https://reviews.freebsd.org/D11963
2017-08-13 18:10:24 +00:00
config_intrhook.9 config_intrhook_establish.9 \
config_intrhook.9 config_intrhook_oneshot.9
Add malloc_domainset(9) and _domainset variants to other allocator KPIs. Remove malloc_domain(9) and most other _domain KPIs added in r327900. The new functions allow the caller to specify a general NUMA domain selection policy, rather than specifically requesting an allocation from a specific domain. The latter policy tends to interact poorly with M_WAITOK, resulting in situations where a caller is blocked indefinitely because the specified domain is depleted. Most existing consumers of the _domain KPIs are converted to instead use a DOMAINSET_PREF() policy, in which we fall back to other domains to satisfy the allocation request. This change also defines a set of DOMAINSET_FIXED() policies, which only permit allocations from the specified domain. Discussed with: gallatin, jeff Reported and tested by: pho (previous version) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17418
2018-10-30 18:26:34 +00:00
MLINKS+=contigmalloc.9 contigmalloc_domainset.9 \
contigmalloc.9 contigfree.9
Add fueword(9) and casueword(9) functions. They are like fuword(9) and casuword(9), but do not mix value read and indication of fault. I know (or remember) enough assembly to handle x86 and powerpc. For arm, mips and sparc64, implement fueword() and casueword() as wrappers around fuword() and casuword(), which means that the functions cannot distinguish between -1 and fault. On architectures where fueword() and casueword() are native, implement fuword() and casuword() using fueword() and casuword(), to reduce assembly code duplication. Sponsored by: The FreeBSD Foundation Tested by: pho MFC after: 2 weeks (ia64 needs treating)
2014-10-28 15:22:13 +00:00
MLINKS+=casuword.9 casueword.9 \
casuword.9 casueword32.9 \
casuword.9 casuword32.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=copy.9 copyin.9 \
Document copyin_nofault, copyout_nofault, uiomove_nofault. Submitted by: alc
2011-07-09 15:24:12 +00:00
copy.9 copyin_nofault.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
copy.9 copyinstr.9 \
copy.9 copyout.9 \
Document copyin_nofault, copyout_nofault, uiomove_nofault. Submitted by: alc
2011-07-09 15:24:12 +00:00
copy.9 copyout_nofault.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
copy.9 copystr.9
Merge from projects/counters: counter(9). Introduce counter(9) API, that implements fast and raceless counters, provided (but not limited to) for gathering of statistical data. See http://lists.freebsd.org/pipermail/freebsd-arch/2013-April/014204.html for more details. In collaboration with: kib Reviewed by: luigi Tested by: ae, ray Sponsored by: Nginx, Inc.
2013-04-08 19:40:53 +00:00
MLINKS+=counter.9 counter_u64_alloc.9 \
counter.9 counter_u64_free.9 \
counter.9 counter_u64_add.9 \
counter.9 counter_enter.9 \
counter.9 counter_exit.9 \
counter.9 counter_u64_add_protected.9 \
counter.9 counter_u64_fetch.9 \
Improve the implementation and documentation of the SYSCTL_COUNTER_U64_ARRAY() macro. - Add proper asserts to the SYSCTL_COUNTER_U64_ARRAY() macro that checks the size of the first element of the array. - Add an example to the counter(9) manual page how to use the SYSCTL_COUNTER_U64_ARRAY() macro. - Add some missing symbolic links for counter(9) while at it.
2016-03-16 08:37:52 +00:00
counter.9 counter_u64_zero.9 \
counter.9 SYSCTL_COUNTER_U64.9 \
counter.9 SYSCTL_ADD_COUNTER_U64.9 \
counter.9 SYSCTL_COUNTER_U64_ARRAY.9 \
counter.9 SYSCTL_ADD_COUNTER_U64_ARRAY.9
Document cpuset(9) A follow-up to r289467. Coerced by: jhb Sponsored by: EMC / Isilon Storage Division
2015-10-20 23:48:14 +00:00
MLINKS+=cpuset.9 CPUSET_T_INITIALIZER.9 \
cpuset.9 CPUSET_FSET.9 \
cpuset.9 CPU_CLR.9 \
cpuset.9 CPU_COPY.9 \
cpuset.9 CPU_ISSET.9 \
cpuset.9 CPU_SET.9 \
cpuset.9 CPU_ZERO.9 \
cpuset.9 CPU_FILL.9 \
cpuset.9 CPU_SETOF.9 \
cpuset.9 CPU_EMPTY.9 \
cpuset.9 CPU_ISFULLSET.9 \
cpuset.9 CPU_FFS.9 \
cpuset.9 CPU_COUNT.9 \
cpuset.9 CPU_SUBSET.9 \
cpuset.9 CPU_OVERLAP.9 \
cpuset.9 CPU_CMP.9 \
cpuset.9 CPU_OR.9 \
cpuset.9 CPU_AND.9 \
bitset: rename confusing macro NAND to ANDNOT s/BIT_NAND/BIT_ANDNOT/, and for CPU and DOMAINSET too. The actual implementation is "and not" (or "but not"), i.e. A but not B. Fortunately this does appear to be what all existing callers want. Don't supply a NAND (not (A and B)) operation at this time. Discussed with: jeff Reviewed by: cem Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D22791
2019-12-13 09:32:16 +00:00
cpuset.9 CPU_ANDNOT.9 \
Document cpuset(9) A follow-up to r289467. Coerced by: jhb Sponsored by: EMC / Isilon Storage Division
2015-10-20 23:48:14 +00:00
cpuset.9 CPU_CLR_ATOMIC.9 \
cpuset.9 CPU_SET_ATOMIC.9 \
cpuset.9 CPU_SET_ATOMIC_ACQ.9 \
cpuset.9 CPU_AND_ATOMIC.9 \
cpuset.9 CPU_OR_ATOMIC.9 \
cpuset.9 CPU_COPY_STORE_REL.9
Update this manpage: - Remove references to cpu_critical_*() as they no longer exist. - Explain that any preemptions that occur during a critical section are deferred until the current thread exits the section. - Remove a bogus example usage of a critical section. - Note that one can interlock critical sections with spin mutexes in certain situations. MFC after: 3 days
2005-10-05 19:48:21 +00:00
MLINKS+=critical_enter.9 critical.9 \
Sort MLINKS.
2005-09-28 07:32:43 +00:00
critical_enter.9 critical_exit.9
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
MLINKS+=crypto_asym.9 crypto_kdispatch.9 \
crypto_asym.9 crypto_kdone.9 \
crypto_asym.9 crypto_kregister.9 \
crypto_asym.9 CRYPTODEV_KPROCESS.9
Add support for optional separate output buffers to in-kernel crypto. Some crypto consumers such as GELI and KTLS for file-backed sendfile need to store their output in a separate buffer from the input. Currently these consumers copy the contents of the input buffer into the output buffer and queue an in-place crypto operation on the output buffer. Using a separate output buffer avoids this copy. - Create a new 'struct crypto_buffer' describing a crypto buffer containing a type and type-specific fields. crp_ilen is gone, instead buffers that use a flat kernel buffer have a cb_buf_len field for their length. The length of other buffer types is inferred from the backing store (e.g. uio_resid for a uio). Requests now have two such structures: crp_buf for the input buffer, and crp_obuf for the output buffer. - Consumers now use helper functions (crypto_use_*, e.g. crypto_use_mbuf()) to configure the input buffer. If an output buffer is not configured, the request still modifies the input buffer in-place. A consumer uses a second set of helper functions (crypto_use_output_*) to configure an output buffer. - Consumers must request support for separate output buffers when creating a crypto session via the CSP_F_SEPARATE_OUTPUT flag and are only permitted to queue a request with a separate output buffer on sessions with this flag set. Existing drivers already reject sessions with unknown flags, so this permits drivers to be modified to support this extension without requiring all drivers to change. - Several data-related functions now have matching versions that operate on an explicit buffer (e.g. crypto_apply_buf, crypto_contiguous_subsegment_buf, bus_dma_load_crp_buf). - Most of the existing data-related functions operate on the input buffer. However crypto_copyback always writes to the output buffer if a request uses a separate output buffer. - For the regions in input/output buffers, the following conventions are followed: - AAD and IV are always present in input only and their fields are offsets into the input buffer. - payload is always present in both buffers. If a request uses a separate output buffer, it must set a new crp_payload_start_output field to the offset of the payload in the output buffer. - digest is in the input buffer for verify operations, and in the output buffer for compute operations. crp_digest_start is relative to the appropriate buffer. - Add a crypto buffer cursor abstraction. This is a more general form of some bits in the cryptosoft driver that tried to always use uio's. However, compared to the original code, this avoids rewalking the uio iovec array for requests with multiple vectors. It also avoids allocate an iovec array for mbufs and populating it by instead walking the mbuf chain directly. - Update the cryptosoft(4) driver to support separate output buffers making use of the cursor abstraction. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24545
2020-05-25 22:12:04 +00:00
MLINKS+=crypto_buffer.9 crypto_apply.9 \
crypto_buffer.9 crypto_apply_buf.9 \
crypto_buffer.9 crypto_buffer_contiguous_segment.9 \
crypto_buffer.9 crypto_buffer_len.9 \
crypto_buffer.9 crypto_contiguous_segment.9 \
crypto_buffer.9 crypto_cursor_init.9 \
crypto_buffer.9 crypto_cursor_advance.9 \
crypto_buffer.9 crypto_cursor_copyback.9 \
crypto_buffer.9 crypto_cursor_copydata.9 \
crypto_buffer.9 crypto_cursor_copydata_noadv.9 \
crypto_buffer.9 crypto_cursor_segbase.9 \
crypto_buffer.9 crypto_cursor_seglen.9 \
crypto_buffer.9 CRYPTO_HAS_OUTPUT_BUFFER.9
MLINKS+=crypto_driver.9 crypto_copyback.9 \
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
crypto_driver.9 crypto_copydata.9 \
crypto_driver.9 crypto_done.9 \
crypto_driver.9 crypto_get_driverid.9 \
crypto_driver.9 crypto_get_driver_session.9 \
Retire the CRYPTO_F_IV_GENERATE flag. The sole in-tree user of this flag has been retired, so remove this complexity from all drivers. While here, add a helper routine drivers can use to read the current request's IV into a local buffer. Use this routine to replace duplicated code in nearly all drivers. Reviewed by: cem Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24450
2020-04-20 22:24:49 +00:00
crypto_driver.9 crypto_read_iv.9 \
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
crypto_driver.9 crypto_unblock.9 \
crypto_driver.9 crypto_unregister_all.9 \
crypto_driver.9 CRYPTODEV_FREESESSION.9 \
crypto_driver.9 CRYPTODEV_NEWSESSION.9 \
crypto_driver.9 CRYPTODEV_PROBESESSION.9 \
crypto_driver.9 CRYPTODEV_PROCESS.9 \
crypto_driver.9 hmac_init_ipad.9 \
crypto_driver.9 hmac_init_opad.9
Add crypto_initreq() and crypto_destroyreq(). These routines are similar to crypto_getreq() and crypto_freereq() but operate on caller-supplied storage instead of allocating crypto requests from a UMA zone. Reviewed by: markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D25691
2020-07-16 21:30:46 +00:00
MLINKS+=crypto_request.9 crypto_destroyreq.9 \
crypto_request.9 crypto_dispatch.9 \
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
crypto_request.9 crypto_freereq.9 \
Add support for optional separate output buffers to in-kernel crypto. Some crypto consumers such as GELI and KTLS for file-backed sendfile need to store their output in a separate buffer from the input. Currently these consumers copy the contents of the input buffer into the output buffer and queue an in-place crypto operation on the output buffer. Using a separate output buffer avoids this copy. - Create a new 'struct crypto_buffer' describing a crypto buffer containing a type and type-specific fields. crp_ilen is gone, instead buffers that use a flat kernel buffer have a cb_buf_len field for their length. The length of other buffer types is inferred from the backing store (e.g. uio_resid for a uio). Requests now have two such structures: crp_buf for the input buffer, and crp_obuf for the output buffer. - Consumers now use helper functions (crypto_use_*, e.g. crypto_use_mbuf()) to configure the input buffer. If an output buffer is not configured, the request still modifies the input buffer in-place. A consumer uses a second set of helper functions (crypto_use_output_*) to configure an output buffer. - Consumers must request support for separate output buffers when creating a crypto session via the CSP_F_SEPARATE_OUTPUT flag and are only permitted to queue a request with a separate output buffer on sessions with this flag set. Existing drivers already reject sessions with unknown flags, so this permits drivers to be modified to support this extension without requiring all drivers to change. - Several data-related functions now have matching versions that operate on an explicit buffer (e.g. crypto_apply_buf, crypto_contiguous_subsegment_buf, bus_dma_load_crp_buf). - Most of the existing data-related functions operate on the input buffer. However crypto_copyback always writes to the output buffer if a request uses a separate output buffer. - For the regions in input/output buffers, the following conventions are followed: - AAD and IV are always present in input only and their fields are offsets into the input buffer. - payload is always present in both buffers. If a request uses a separate output buffer, it must set a new crp_payload_start_output field to the offset of the payload in the output buffer. - digest is in the input buffer for verify operations, and in the output buffer for compute operations. crp_digest_start is relative to the appropriate buffer. - Add a crypto buffer cursor abstraction. This is a more general form of some bits in the cryptosoft driver that tried to always use uio's. However, compared to the original code, this avoids rewalking the uio iovec array for requests with multiple vectors. It also avoids allocate an iovec array for mbufs and populating it by instead walking the mbuf chain directly. - Update the cryptosoft(4) driver to support separate output buffers making use of the cursor abstraction. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24545
2020-05-25 22:12:04 +00:00
crypto_request.9 crypto_getreq.9 \
Add crypto_initreq() and crypto_destroyreq(). These routines are similar to crypto_getreq() and crypto_freereq() but operate on caller-supplied storage instead of allocating crypto requests from a UMA zone. Reviewed by: markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D25691
2020-07-16 21:30:46 +00:00
crypto_request.9 crypto_initreq.9 \
Add support for optional separate output buffers to in-kernel crypto. Some crypto consumers such as GELI and KTLS for file-backed sendfile need to store their output in a separate buffer from the input. Currently these consumers copy the contents of the input buffer into the output buffer and queue an in-place crypto operation on the output buffer. Using a separate output buffer avoids this copy. - Create a new 'struct crypto_buffer' describing a crypto buffer containing a type and type-specific fields. crp_ilen is gone, instead buffers that use a flat kernel buffer have a cb_buf_len field for their length. The length of other buffer types is inferred from the backing store (e.g. uio_resid for a uio). Requests now have two such structures: crp_buf for the input buffer, and crp_obuf for the output buffer. - Consumers now use helper functions (crypto_use_*, e.g. crypto_use_mbuf()) to configure the input buffer. If an output buffer is not configured, the request still modifies the input buffer in-place. A consumer uses a second set of helper functions (crypto_use_output_*) to configure an output buffer. - Consumers must request support for separate output buffers when creating a crypto session via the CSP_F_SEPARATE_OUTPUT flag and are only permitted to queue a request with a separate output buffer on sessions with this flag set. Existing drivers already reject sessions with unknown flags, so this permits drivers to be modified to support this extension without requiring all drivers to change. - Several data-related functions now have matching versions that operate on an explicit buffer (e.g. crypto_apply_buf, crypto_contiguous_subsegment_buf, bus_dma_load_crp_buf). - Most of the existing data-related functions operate on the input buffer. However crypto_copyback always writes to the output buffer if a request uses a separate output buffer. - For the regions in input/output buffers, the following conventions are followed: - AAD and IV are always present in input only and their fields are offsets into the input buffer. - payload is always present in both buffers. If a request uses a separate output buffer, it must set a new crp_payload_start_output field to the offset of the payload in the output buffer. - digest is in the input buffer for verify operations, and in the output buffer for compute operations. crp_digest_start is relative to the appropriate buffer. - Add a crypto buffer cursor abstraction. This is a more general form of some bits in the cryptosoft driver that tried to always use uio's. However, compared to the original code, this avoids rewalking the uio iovec array for requests with multiple vectors. It also avoids allocate an iovec array for mbufs and populating it by instead walking the mbuf chain directly. - Update the cryptosoft(4) driver to support separate output buffers making use of the cursor abstraction. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D24545
2020-05-25 22:12:04 +00:00
crypto_request.9 crypto_use_buf.9 \
crypto_request.9 crypto_use_mbuf.9 \
crypto_request.9 crypto_use_output_buf.9 \
crypto_request.9 crypto_use_output_mbuf.9 \
crypto_request.9 crypto_use_output_uio.9 \
Remove an extraneous line continuation from r361481.
2020-05-25 23:07:50 +00:00
crypto_request.9 crypto_use_uio.9
Refactor driver and consumer interfaces for OCF (in-kernel crypto). - The linked list of cryptoini structures used in session initialization is replaced with a new flat structure: struct crypto_session_params. This session includes a new mode to define how the other fields should be interpreted. Available modes include: - COMPRESS (for compression/decompression) - CIPHER (for simply encryption/decryption) - DIGEST (computing and verifying digests) - AEAD (combined auth and encryption such as AES-GCM and AES-CCM) - ETA (combined auth and encryption using encrypt-then-authenticate) Additional modes could be added in the future (e.g. if we wanted to support TLS MtE for AES-CBC in the kernel we could add a new mode for that. TLS modes might also affect how AAD is interpreted, etc.) The flat structure also includes the key lengths and algorithms as before. However, code doesn't have to walk the linked list and switch on the algorithm to determine which key is the auth key vs encryption key. The 'csp_auth_*' fields are always used for auth keys and settings and 'csp_cipher_*' for cipher. (Compression algorithms are stored in csp_cipher_alg.) - Drivers no longer register a list of supported algorithms. This doesn't quite work when you factor in modes (e.g. a driver might support both AES-CBC and SHA2-256-HMAC separately but not combined for ETA). Instead, a new 'crypto_probesession' method has been added to the kobj interface for symmteric crypto drivers. This method returns a negative value on success (similar to how device_probe works) and the crypto framework uses this value to pick the "best" driver. There are three constants for hardware (e.g. ccr), accelerated software (e.g. aesni), and plain software (cryptosoft) that give preference in that order. One effect of this is that if you request only hardware when creating a new session, you will no longer get a session using accelerated software. Another effect is that the default setting to disallow software crypto via /dev/crypto now disables accelerated software. Once a driver is chosen, 'crypto_newsession' is invoked as before. - Crypto operations are now solely described by the flat 'cryptop' structure. The linked list of descriptors has been removed. A separate enum has been added to describe the type of data buffer in use instead of using CRYPTO_F_* flags to make it easier to add more types in the future if needed (e.g. wired userspace buffers for zero-copy). It will also make it easier to re-introduce separate input and output buffers (in-kernel TLS would benefit from this). Try to make the flags related to IV handling less insane: - CRYPTO_F_IV_SEPARATE means that the IV is stored in the 'crp_iv' member of the operation structure. If this flag is not set, the IV is stored in the data buffer at the 'crp_iv_start' offset. - CRYPTO_F_IV_GENERATE means that a random IV should be generated and stored into the data buffer. This cannot be used with CRYPTO_F_IV_SEPARATE. If a consumer wants to deal with explicit vs implicit IVs, etc. it can always generate the IV however it needs and store partial IVs in the buffer and the full IV/nonce in crp_iv and set CRYPTO_F_IV_SEPARATE. The layout of the buffer is now described via fields in cryptop. crp_aad_start and crp_aad_length define the boundaries of any AAD. Previously with GCM and CCM you defined an auth crd with this range, but for ETA your auth crd had to span both the AAD and plaintext (and they had to be adjacent). crp_payload_start and crp_payload_length define the boundaries of the plaintext/ciphertext. Modes that only do a single operation (COMPRESS, CIPHER, DIGEST) should only use this region and leave the AAD region empty. If a digest is present (or should be generated), it's starting location is marked by crp_digest_start. Instead of using the CRD_F_ENCRYPT flag to determine the direction of the operation, cryptop now includes an 'op' field defining the operation to perform. For digests I've added a new VERIFY digest mode which assumes a digest is present in the input and fails the request with EBADMSG if it doesn't match the internally-computed digest. GCM and CCM already assumed this, and the new AEAD mode requires this for decryption. The new ETA mode now also requires this for decryption, so IPsec and GELI no longer do their own authentication verification. Simple DIGEST operations can also do this, though there are no in-tree consumers. To eventually support some refcounting to close races, the session cookie is now passed to crypto_getop() and clients should no longer set crp_sesssion directly. - Assymteric crypto operation structures should be allocated via crypto_getkreq() and freed via crypto_freekreq(). This permits the crypto layer to track open asym requests and close races with a driver trying to unregister while asym requests are in flight. - crypto_copyback, crypto_copydata, crypto_apply, and crypto_contiguous_subsegment now accept the 'crp' object as the first parameter instead of individual members. This makes it easier to deal with different buffer types in the future as well as separate input and output buffers. It's also simpler for driver writers to use. - bus_dmamap_load_crp() loads a DMA mapping for a crypto buffer. This understands the various types of buffers so that drivers that use DMA do not have to be aware of different buffer types. - Helper routines now exist to build an auth context for HMAC IPAD and OPAD. This reduces some duplicated work among drivers. - Key buffers are now treated as const throughout the framework and in device drivers. However, session key buffers provided when a session is created are expected to remain alive for the duration of the session. - GCM and CCM sessions now only specify a cipher algorithm and a cipher key. The redundant auth information is not needed or used. - For cryptosoft, split up the code a bit such that the 'process' callback now invokes a function pointer in the session. This function pointer is set based on the mode (in effect) though it simplifies a few edge cases that would otherwise be in the switch in 'process'. It does split up GCM vs CCM which I think is more readable even if there is some duplication. - I changed /dev/crypto to support GMAC requests using CRYPTO_AES_NIST_GMAC as an auth algorithm and updated cryptocheck to work with it. - Combined cipher and auth sessions via /dev/crypto now always use ETA mode. The COP_F_CIPHER_FIRST flag is now a no-op that is ignored. This was actually documented as being true in crypto(4) before, but the code had not implemented this before I added the CIPHER_FIRST flag. - I have not yet updated /dev/crypto to be aware of explicit modes for sessions. I will probably do that at some point in the future as well as teach it about IV/nonce and tag lengths for AEAD so we can support all of the NIST KAT tests for GCM and CCM. - I've split up the exising crypto.9 manpage into several pages of which many are written from scratch. - I have converted all drivers and consumers in the tree and verified that they compile, but I have not tested all of them. I have tested the following drivers: - cryptosoft - aesni (AES only) - blake2 - ccr and the following consumers: - cryptodev - IPsec - ktls_ocf - GELI (lightly) I have not tested the following: - ccp - aesni with sha - hifn - kgssapi_krb5 - ubsec - padlock - safe - armv8_crypto (aarch64) - glxsb (i386) - sec (ppc) - cesa (armv7) - cryptocteon (mips64) - nlmsec (mips64) Discussed with: cem Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D23677
2020-03-27 18:25:23 +00:00
MLINKS+=crypto_session.9 crypto_auth_hash.9 \
crypto_session.9 crypto_cipher.9 \
crypto_session.9 crypto_get_params.9 \
crypto_session.9 crypto_newsession.9 \
crypto_session.9 crypto_freesession.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=DB_COMMAND.9 DB_SHOW_ALL_COMMAND.9 \
DB_COMMAND.9 DB_SHOW_COMMAND.9
Add DECLARE_MODULE_TIED mlink missed in r329244 Reported by: imp
2018-02-13 21:33:40 +00:00
MLINKS+=DECLARE_MODULE.9 DECLARE_MODULE_TIED.9
Connect dev_clone.9 and devfs_set_cdevpriv.9 to the build.
2008-09-15 10:12:04 +00:00
MLINKS+=dev_clone.9 drain_dev_clone_events.9
Add a dev_refthread.9 document. Reviewed by: kib Sponsored by: Dell EMC Isilon Differential: https://reviews.freebsd.org/D16897
2018-10-20 20:41:25 +00:00
MLINKS+=dev_refthread.9 devvn_refthread.9 \
dev_refthread.9 dev_relthread.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=devfs_set_cdevpriv.9 devfs_clear_cdevpriv.9 \
devfs_set_cdevpriv.9 devfs_get_cdevpriv.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=device_add_child.9 device_add_child_ordered.9
MLINKS+=device_enable.9 device_disable.9 \
device_enable.9 device_is_enabled.9
MLINKS+=device_get_ivars.9 device_set_ivars.9
MLINKS+=device_get_name.9 device_get_nameunit.9
MLINKS+=device_get_state.9 device_busy.9 \
device_get_state.9 device_is_alive.9 \
device_get_state.9 device_is_attached.9 \
device_get_state.9 device_unbusy.9
Add a stub man page for device_get_sysctl{_ctx,tree}. Needs some work, but is better than nothing. Any help appreciated.
2006-05-23 22:11:20 +00:00
MLINKS+=device_get_sysctl.9 device_get_sysctl_ctx.9 \
device_get_sysctl.9 device_get_sysctl_tree.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=device_quiet.9 device_is_quiet.9 \
device_quiet.9 device_verbose.9
MLINKS+=device_set_desc.9 device_get_desc.9 \
device_set_desc.9 device_set_desc_copy.9
MLINKS+=device_set_flags.9 device_get_flags.9
MLINKS+=devstat.9 devicestat.9 \
devstat(9): Update the man page to reflect the current implementation - Rename devstat_add_entry to devstat_new_entry - Update the description of devstat_trans_flags - Add manpage aliases for devstat_start_transaction_bio and devstat_end_transaction_bio PR: 157316 Submitted by: novel Reviewed by: cem, bcr (mentor) Approved by: bcr (mentor) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25677
2020-07-17 22:15:02 +00:00
devstat.9 devstat_new_entry.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
devstat.9 devstat_end_transaction.9 \
devstat(9): Update the man page to reflect the current implementation - Rename devstat_add_entry to devstat_new_entry - Update the description of devstat_trans_flags - Add manpage aliases for devstat_start_transaction_bio and devstat_end_transaction_bio PR: 157316 Submitted by: novel Reviewed by: cem, bcr (mentor) Approved by: bcr (mentor) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25677
2020-07-17 22:15:02 +00:00
devstat.9 devstat_end_transaction_bio.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
devstat.9 devstat_remove_entry.9 \
devstat(9): Update the man page to reflect the current implementation - Rename devstat_add_entry to devstat_new_entry - Update the description of devstat_trans_flags - Add manpage aliases for devstat_start_transaction_bio and devstat_end_transaction_bio PR: 157316 Submitted by: novel Reviewed by: cem, bcr (mentor) Approved by: bcr (mentor) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25677
2020-07-17 22:15:02 +00:00
devstat.9 devstat_start_transaction.9 \
devstat.9 devstat_start_transaction_bio.9
Add missing MLINKS for disk_add_alias(9). MFC after: 2 weeks
2017-11-04 16:23:34 +00:00
MLINKS+=disk.9 disk_add_alias.9 \
disk.9 disk_alloc.9 \
Mention disk_gone() in disk(9). Approved by: rwatson (mentor)
2009-02-22 13:38:16 +00:00
disk.9 disk_create.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
disk.9 disk_destroy.9 \
Document disk_resize(9).
2012-10-30 13:05:50 +00:00
disk.9 disk_gone.9 \
disk.9 disk_resize.9
Add man page for dnvlist. Submitted by: Adam Starak <starak.adam@gmail.com> Reviewed by: cem, wblock
2016-10-05 19:01:00 +00:00
MLINKS+=dnv.9 dnvlist.9 \
dnv.9 dnvlist_get_binary.9 \
dnv.9 dnvlist_get_bool.9 \
dnv.9 dnvlist_get_descriptor.9 \
dnv.9 dnvlist_get_number.9 \
dnv.9 dnvlist_get_nvlist.9 \
dnv.9 dnvlist_get_string.9 \
dnv.9 dnvlist_take_binary.9 \
dnv.9 dnvlist_take_bool.9 \
dnv.9 dnvlist_take_descriptor.9 \
dnv.9 dnvlist_take_number.9 \
dnv.9 dnvlist_take_nvlist.9 \
dnv.9 dnvlist_take_string.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=domain.9 DOMAIN_SET.9 \
Catch up with r195837 (2.5 years ago) which renamed net_add_domain() to domain_add(). PR: 165424 Submitted by: Lachlan Kang MFC after: 1 week
2012-02-23 17:47:19 +00:00
domain.9 domain_add.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
domain.9 pfctlinput.9 \
Sort MAN and MLINKS lists.
2006-10-05 12:40:44 +00:00
domain.9 pfctlinput2.9 \
Document pffinddomain(). Reviewed by: glebius
2012-12-07 02:29:32 +00:00
domain.9 pffinddomain.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
domain.9 pffindproto.9 \
domain.9 pffindtype.9
Manpages for the buf_ring and drbr interfaces. Submitted by: kmacy (aeons ago) MFC after: 1 week
2012-01-30 21:02:25 +00:00
MLINKS+=drbr.9 drbr_free.9 \
drbr.9 drbr_enqueue.9 \
drbr.9 drbr_dequeue.9 \
drbr.9 drbr_dequeue_cond.9 \
drbr.9 drbr_flush.9 \
drbr.9 drbr_empty.9 \
drbr.9 drbr_inuse.9 \
drbr.9 drbr_stats_update.9
Document DRIVER_MODULE_ORDERED, EARLY_DRIVER_MODULE, and EARLY_DRIVER_MODULE_ORDERED.
2012-08-21 17:58:39 +00:00
MLINKS+=DRIVER_MODULE.9 DRIVER_MODULE_ORDERED.9 \
DRIVER_MODULE.9 EARLY_DRIVER_MODULE.9 \
DRIVER_MODULE.9 EARLY_DRIVER_MODULE_ORDERED.9
Implement API for draining EPOCH(9) callbacks. The epoch_drain_callbacks() function is used to drain all pending callbacks which have been invoked by prior epoch_call() function calls on the same epoch. This function is useful when there are shared memory structure(s) referred to by the epoch callback(s) which are not refcounted and are rarely freed. The typical place for calling this function is right before freeing or invalidating the shared resource(s) used by the epoch callback(s). This function can sleep and is not optimized for performance. Differential Revision: https://reviews.freebsd.org/D20109 MFC after: 1 week Sponsored by: Mellanox Technologies
2019-06-28 10:38:56 +00:00
MLINKS+=epoch.9 epoch_context.9 \
epoch.9 epoch_alloc.9 \
epoch.9 epoch_free.9 \
epoch.9 epoch_enter.9 \
epoch.9 epoch_exit.9 \
epoch.9 epoch_wait.9 \
epoch.9 epoch_call.9 \
epoch.9 epoch_drain_callbacks.9 \
epoch.9 in_epoch.9
Add a manual page for the kernel's EVENTHANDLER facility. Reviewed by: ru
2004-12-03 14:05:55 +00:00
MLINKS+=EVENTHANDLER.9 EVENTHANDLER_DECLARE.9 \
Document EVENTHANDLER_DEFINE(9). MFC after: 2 weeks Sponsored by: DARPA, AFRL
2017-03-27 20:32:12 +00:00
EVENTHANDLER.9 EVENTHANDLER_DEFINE.9 \
Add a manual page for the kernel's EVENTHANDLER facility. Reviewed by: ru
2004-12-03 14:05:55 +00:00
EVENTHANDLER.9 EVENTHANDLER_DEREGISTER.9 \
EVENTHANDLER.9 eventhandler_deregister.9 \
Sort MLINKS.
2005-09-28 07:32:43 +00:00
EVENTHANDLER.9 eventhandler_find_list.9 \
Add a manual page for the kernel's EVENTHANDLER facility. Reviewed by: ru
2004-12-03 14:05:55 +00:00
EVENTHANDLER.9 EVENTHANDLER_INVOKE.9 \
Sort MLINKS.
2005-09-28 07:32:43 +00:00
EVENTHANDLER.9 eventhandler_prune_list.9 \
Add a manual page for the kernel's EVENTHANDLER facility. Reviewed by: ru
2004-12-03 14:05:55 +00:00
EVENTHANDLER.9 EVENTHANDLER_REGISTER.9 \
Sort MLINKS.
2005-09-28 07:32:43 +00:00
EVENTHANDLER.9 eventhandler_register.9
Add eventtimers(9) man page, describing related KPIs. Sponsored by: iXsystems, Inc. MFC after: 1 month
2011-12-20 11:40:22 +00:00
MLINKS+=eventtimers.9 et_register.9 \
eventtimers.9 et_deregister.9 \
eventtimers.9 et_ban.9 \
eventtimers.9 et_find.9 \
eventtimers.9 et_free.9 \
eventtimers.9 et_init.9 \
eventtimers.9 ET_LOCK.9 \
eventtimers.9 ET_UNLOCK.9 \
eventtimers.9 et_start.9 \
eventtimers.9 et_stop.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=fail.9 KFAIL_POINT_CODE.9 \
fail.9 KFAIL_POINT_ERROR.9 \
fail.9 KFAIL_POINT_GOTO.9 \
fail.9 KFAIL_POINT_RETURN.9 \
fail.9 KFAIL_POINT_RETURN_VOID.9
[fdt_pinctrl] Add man pages for fdt_pinctrl driver - Add fdt_pinctrl(4) with general information for the driver - Add fdt_pinctrl(9) with fdt_pinctrl KPI description Reviewed by: ian, manu, wblock MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D14235
2018-03-03 02:49:49 +00:00
MLINKS+=fdt_pinctrl.9 fdt_pinctrl_configure.9 \
fdt_pinctrl.9 fdt_pinctrl_configure_by_name.9 \
fdt_pinctrl.9 fdt_pinctrl_configure_tree.9 \
fdt_pinctrl.9 fdt_pinctrl_register.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=fetch.9 fubyte.9 \
Make fetch(9) and store(9) manual pages closer to reality.
2009-10-05 15:16:28 +00:00
fetch.9 fuword.9 \
fetch.9 fuword16.9 \
fetch.9 fuword32.9 \
Add fueword(9) and casueword(9) functions. They are like fuword(9) and casuword(9), but do not mix value read and indication of fault. I know (or remember) enough assembly to handle x86 and powerpc. For arm, mips and sparc64, implement fueword() and casueword() as wrappers around fuword() and casuword(), which means that the functions cannot distinguish between -1 and fault. On architectures where fueword() and casueword() are native, implement fuword() and casuword() using fueword() and casuword(), to reduce assembly code duplication. Sponsored by: The FreeBSD Foundation Tested by: pho MFC after: 2 weeks (ia64 needs treating)
2014-10-28 15:22:13 +00:00
fetch.9 fuword64.9 \
fetch.9 fueword.9 \
fetch.9 fueword32.9 \
fetch.9 fueword64.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=firmware.9 firmware_get.9 \
firmware.9 firmware_put.9 \
firmware.9 firmware_register.9 \
firmware.9 firmware_unregister.9
Add fpu_kern.9 man page to the install. Sponsored by: The FreeBSD Foundation MFC after: 1 week
2014-06-25 07:57:01 +00:00
MLINKS+=fpu_kern.9 fpu_kern_alloc_ctx.9 \
fpu_kern.9 fpu_kern_free_ctx.9 \
fpu_kern.9 fpu_kern_enter.9 \
fpu_kern.9 fpu_kern_leave.9 \
fpu_kern.9 fpu_kern_thread.9 \
fpu_kern.9 is_fpu_kern_thread.9
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
MLINKS+=g_attach.9 g_detach.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=g_bio.9 g_alloc_bio.9 \
g_bio.9 g_clone_bio.9 \
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
g_bio.9 g_destroy_bio.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
g_bio.9 g_duplicate_bio.9 \
GEOM: Reduce unnecessary log interleaving with sbufs Similar to what was done for device_printfs in r347229. Convert g_print_bio() to a thin shim around g_format_bio(), which acts on an sbuf; documented in g_bio.9. Reviewed by: markj Discussed with: rlibby Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D21165
2019-08-07 19:28:35 +00:00
g_bio.9 g_format_bio.9 \
Create symbolic link for g_print_bio(9) manual page. Approved by: scottl (mentor)
2004-02-11 18:43:20 +00:00
g_bio.9 g_new_bio.9 \
Per Ravi Pokala's suggestion, rewrite the g_reset_bio description to be clearer. It also describes it with more nuance. Add missing MLINKS noticed by trasz@. Bump the date.
2016-05-17 17:08:13 +00:00
g_bio.9 g_print_bio.9 \
g_bio.9 g_reset_bio.9
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
MLINKS+=g_consumer.9 g_destroy_consumer.9 \
g_consumer.9 g_new_consumer.9
MLINKS+=g_data.9 g_read_data.9 \
g_data.9 g_write_data.9
Add a manpage for the getenv() family of functions in the kernel.
2013-10-22 20:10:38 +00:00
MLINKS+=getenv.9 freeenv.9 \
getenv.9 getenv_int.9 \
getenv.9 getenv_long.9 \
getenv.9 getenv_string.9 \
getenv.9 getenv_quad.9 \
getenv.9 getenv_uint.9 \
getenv.9 getenv_ulong.9 \
getenv(9): rename to "kern_getenv", etc. Update the documentation to catch up with r273174, which renamed getenv -> kern_getenv setenv -> kern_setenv unsetenv -> kern_unsetenv Leave the old links in place to support finger memory. MFC after: 3 days Sponsored by: Dell EMC
2017-06-01 21:07:25 +00:00
getenv.9 kern_getenv.9 \
getenv.9 kern_setenv.9 \
getenv.9 kern_unsetenv.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
getenv.9 setenv.9 \
getenv.9 testenv.9 \
getenv.9 unsetenv.9
Added GEOM kernel API manuals to the build. Reviewed by: scottl Approved by: phk, scottl (mentor)
2004-02-11 10:09:17 +00:00
MLINKS+=g_event.9 g_cancel_event.9 \
g_event.9 g_post_event.9 \
g_event.9 g_waitfor_event.9
MLINKS+=g_geom.9 g_destroy_geom.9 \
g_geom.9 g_new_geomf.9
MLINKS+=g_provider.9 g_destroy_provider.9 \
g_provider.9 g_error_provider.9 \
g_provider.9 g_new_providerf.9
Connect hash(9) to the build and add MLINKS for all functions. Pointed out by: ru
2006-10-02 11:51:25 +00:00
MLINKS+=hash.9 hash32.9 \
hash.9 hash32_buf.9 \
hash.9 hash32_str.9 \
hash.9 hash32_stre.9 \
Sort MAN and MLINKS lists.
2006-10-05 12:40:44 +00:00
hash.9 hash32_strn.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
hash.9 hash32_strne.9 \
hash.9 jenkins_hash.9 \
hash.9 jenkins_hash32.9
Add a manual page for hashinit(9), hashdestroy(9) and phashinit(9). Reviewed by: ru
2004-10-12 02:36:24 +00:00
MLINKS+=hashinit.9 hashdestroy.9 \
Sort MLINKS.
2007-10-26 11:01:17 +00:00
hashinit.9 hashinit_flags.9 \
hashinit.9 phashinit.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=hhook.9 hhook_head_register.9 \
hhook.9 hhook_head_deregister.9 \
hhook.9 hhook_head_deregister_lookup.9 \
hhook.9 hhook_run_hooks.9 \
hhook.9 HHOOKS_RUN_IF.9 \
hhook.9 HHOOKS_RUN_LOOKUP_IF.9
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
MLINKS+=ieee80211.9 ieee80211_ifattach.9 \
ieee80211.9 ieee80211_ifdetach.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=ieee80211_amrr.9 ieee80211_amrr_choose.9 \
ieee80211_amrr.9 ieee80211_amrr_cleanup.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_amrr.9 ieee80211_amrr_init.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_amrr.9 ieee80211_amrr_node_init.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_amrr.9 ieee80211_amrr_setinterval.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_amrr.9 ieee80211_amrr_tx_complete.9 \
ieee80211_amrr.9 ieee80211_amrr_tx_update.9
MLINKS+=ieee80211_beacon.9 ieee80211_beacon_alloc.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_beacon.9 ieee80211_beacon_notify.9 \
ieee80211_beacon.9 ieee80211_beacon_update.9
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
MLINKS+=ieee80211_bmiss.9 ieee80211_beacon_miss.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=ieee80211_crypto.9 ieee80211_crypto_available.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_crypto.9 ieee80211_crypto_decap.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_crypto.9 ieee80211_crypto_delglobalkeys.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ieee80211_crypto.9 ieee80211_crypto_delkey.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_crypto.9 ieee80211_crypto_demic.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_crypto.9 ieee80211_crypto_encap.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_crypto.9 ieee80211_crypto_enmic.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_crypto.9 ieee80211_crypto_newkey.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_crypto.9 ieee80211_crypto_register.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_crypto.9 ieee80211_crypto_reload_keys.9 \
ieee80211_crypto.9 ieee80211_crypto_setkey.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_crypto.9 ieee80211_crypto_unregister.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_crypto.9 ieee80211_key_update_begin.9 \
ieee80211_crypto.9 ieee80211_key_update_end.9 \
ieee80211_crypto.9 ieee80211_notify_michael_failure.9 \
ieee80211_crypto.9 ieee80211_notify_replay_failure.9
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
MLINKS+=ieee80211_input.9 ieee80211_input_all.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=ieee80211_node.9 ieee80211_dump_node.9 \
ieee80211_node.9 ieee80211_dump_nodes.9 \
ieee80211_node.9 ieee80211_find_rxnode.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_node.9 ieee80211_find_rxnode_withkey.9 \
Initial import of documentation for net80211 interface code. Of particular interest here is the ieee80211_radiotap(9) man page. TODO: Flesh out ieee80211_node.9, ieee80211_proto.9. Submitted by: bms (with help from Darron Broad)
2004-03-04 12:52:10 +00:00
ieee80211_node.9 ieee80211_free_node.9 \
ieee80211_node.9 ieee80211_iterate_nodes.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_node.9 ieee80211_ref_node.9 \
ieee80211_node.9 ieee80211_unref_node.9
MLINKS+=ieee80211_output.9 ieee80211_process_callback.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_output.9 M_SEQNO_GET.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_output.9 M_WME_GETAC.9
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
MLINKS+=ieee80211_proto.9 ieee80211_new_state.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_proto.9 ieee80211_resume_all.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_proto.9 ieee80211_start_all.9 \
ieee80211_proto.9 ieee80211_stop_all.9 \
ieee80211_proto.9 ieee80211_suspend_all.9 \
ieee80211_proto.9 ieee80211_waitfor_parent.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=ieee80211_radiotap.9 ieee80211_radiotap_active.9 \
First (early) draft of net80211 documentation. Note this is focused on driver writers (as opposed to folks adding to net80211). Reviewed by: wkoszek Approved by: re (rwatson)
2009-08-12 21:03:16 +00:00
ieee80211_radiotap.9 ieee80211_radiotap_active_vap.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
ieee80211_radiotap.9 ieee80211_radiotap_attach.9 \
ieee80211_radiotap.9 ieee80211_radiotap_tx.9 \
ieee80211_radiotap.9 radiotap.9
MLINKS+=ieee80211_regdomain.9 ieee80211_alloc_countryie.9 \
ieee80211_regdomain.9 ieee80211_init_channels.9 \
ieee80211_regdomain.9 ieee80211_sort_channels.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=ieee80211_scan.9 ieee80211_add_scan.9 \
ieee80211_scan.9 ieee80211_bg_scan.9 \
ieee80211_scan.9 ieee80211_cancel_scan.9 \
ieee80211_scan.9 ieee80211_cancel_scan_any.9 \
ieee80211_scan.9 ieee80211_check_scan.9 \
ieee80211_scan.9 ieee80211_check_scan_current.9 \
ieee80211_scan.9 ieee80211_flush.9 \
ieee80211_scan.9 ieee80211_probe_curchan.9 \
ieee80211_scan.9 ieee80211_scan_assoc_fail.9 \
ieee80211_scan.9 ieee80211_scan_done.9 \
ieee80211_scan.9 ieee80211_scan_dump_channels.9 \
ieee80211_scan.9 ieee80211_scan_flush.9 \
ieee80211_scan.9 ieee80211_scan_iterate.9 \
ieee80211_scan.9 ieee80211_scan_next.9 \
ieee80211_scan.9 ieee80211_scan_timeout.9 \
ieee80211_scan.9 ieee80211_scanner_get.9 \
ieee80211_scan.9 ieee80211_scanner_register.9 \
ieee80211_scan.9 ieee80211_scanner_unregister.9 \
ieee80211_scan.9 ieee80211_scanner_unregister_all.9 \
ieee80211_scan.9 ieee80211_start_scan.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=ieee80211_vap.9 ieee80211_vap_attach.9 \
ieee80211_vap.9 ieee80211_vap_detach.9 \
ieee80211_vap.9 ieee80211_vap_setup.9
Add missing MLINKS for functions decribed in iflibdd(9), iflibdi(9), and iflibtxrx(9).
2017-05-24 01:03:30 +00:00
MLINKS+=iflibdd.9 ifdi_attach_pre.9 \
iflibdd.9 ifdi_attach_post.9 \
iflibdd.9 ifdi_detach.9 \
iflibdd.9 ifdi_get_counter.9 \
iflibdd.9 ifdi_i2c_req.9 \
iflibdd.9 ifdi_init.9 \
iflibdd.9 ifdi_intr_enable.9 \
iflibdd.9 ifdi_intr_disable.9 \
iflibdd.9 ifdi_led_func.9 \
iflibdd.9 ifdi_link_intr_enable.9 \
iflibdd.9 ifdi_media_set.9 \
iflibdd.9 ifdi_media_status.9 \
iflibdd.9 ifdi_media_change.9 \
iflibdd.9 ifdi_mtu_set.9 \
iflibdd.9 ifdi_multi_set.9 \
iflibdd.9 ifdi_promisc_set.9 \
iflibdd.9 ifdi_queues_alloc.9 \
iflibdd.9 ifdi_queues_free.9 \
iflibdd.9 ifdi_queue_intr_enable.9 \
iflibdd.9 ifdi_resume.9 \
iflibdd.9 ifdi_rxq_setup.9 \
iflibdd.9 ifdi_stop.9 \
iflibdd.9 ifdi_suspend.9 \
iflibdd.9 ifdi_sysctl_int_delay.9 \
iflibdd.9 ifdi_timer.9 \
iflibdd.9 ifdi_txq_setup.9 \
iflibdd.9 ifdi_update_admin_status.9 \
iflibdd.9 ifdi_vf_add.9 \
iflibdd.9 ifdi_vflr_handle.9 \
iflibdd.9 ifdi_vlan_register.9 \
iflibdd.9 ifdi_vlan_unregister.9 \
iflibdd.9 ifdi_watchdog_reset.9 \
iflibdd.9 iov_init.9 \
iflibdd.9 iov_uinit.9
MLINKS+=iflibdi.9 iflib_add_int_delay_sysctl.9 \
iflibdi.9 iflib_device_attach.9 \
iflibdi.9 iflib_device_deregister.9 \
iflibdi.9 iflib_device_detach.9 \
iflibdi.9 iflib_device_suspend.9 \
iflibdi.9 iflib_device_register.9 \
iflibdi.9 iflib_device_resume.9 \
iflibdi.9 iflib_led_create.9 \
iflibdi.9 iflib_irq_alloc.9 \
iflibdi.9 iflib_irq_alloc_generic.9 \
iflibdi.9 iflib_link_intr_deferred.9 \
iflibdi.9 iflib_link_state_change.9 \
iflibdi.9 iflib_rx_intr_deferred.9 \
iflibdi.9 iflib_tx_intr_deferred.9
MLINKS+=iflibtxrx.9 isc_rxd_available.9 \
iflibtxrx.9 isc_rxd_refill.9 \
iflibtxrx.9 isc_rxd_flush.9 \
iflibtxrx.9 isc_rxd_pkt_get.9 \
iflibtxrx.9 isc_txd_credits_update.9 \
iflibtxrx.9 isc_txd_encap.9 \
iflibtxrx.9 isc_txd_flush.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=ifnet.9 if_addmulti.9 \
ifnet.9 if_alloc.9 \
Track device's NUMA domain in ifnet & alloc ifnet from NUMA local memory This commit adds new if_alloc_domain() and if_alloc_dev() methods to allocate ifnets. When called with a domain on a NUMA machine, ifalloc_domain() will record the NUMA domain in the ifnet, and it will allocate the ifnet struct from memory which is local to that NUMA node. Similarly, if_alloc_dev() is a wrapper for if_alloc_domain which uses a driver supplied device_t to call ifalloc_domain() with the appropriate domain. Note that the new if_numa_domain field fits in an alignment pad in struct ifnet, and so does not alter the size of the structure. Reviewed by: glebius, kib, markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D19930
2019-04-22 19:24:21 +00:00
ifnet.9 if_alloc_dev.9 \
ifnet.9 if_alloc_domain.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ifnet.9 if_allmulti.9 \
ifnet.9 if_attach.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
ifnet.9 if_data.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ifnet.9 IF_DEQUEUE.9 \
ifnet.9 if_delmulti.9 \
ifnet.9 if_detach.9 \
ifnet.9 if_down.9 \
ifnet.9 if_findmulti.9 \
ifnet.9 if_free.9 \
ifnet.9 if_free_type.9 \
ifnet.9 if_up.9 \
ifnet.9 ifa_free.9 \
ifnet.9 ifa_ifwithaddr.9 \
ifnet.9 ifa_ifwithdstaddr.9 \
ifnet.9 ifa_ifwithnet.9 \
ifnet.9 ifa_ref.9 \
ifnet.9 ifaddr.9 \
ifnet.9 ifaddr_byindex.9 \
ifnet.9 ifaof_ifpforaddr.9 \
ifnet.9 ifioctl.9 \
ifnet.9 ifpromisc.9 \
ifnet.9 ifqueue.9 \
ifnet.9 ifunit.9 \
ifnet.9 ifunit_ref.9
Add missing mlink for insmntque1(). MFC after: 1 week
2010-08-22 16:42:46 +00:00
MLINKS+=insmntque.9 insmntque1.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=ithread.9 ithread_add_handler.9 \
ithread.9 ithread_create.9 \
ithread.9 ithread_destroy.9 \
ithread.9 ithread_priority.9 \
ithread.9 ithread_remove_handler.9 \
ithread.9 ithread_schedule.9
Sorted lists. Use the same style as most Makefiles for `MLINKS+=' lines.
1998-01-01 10:12:14 +00:00
MLINKS+=kernacc.9 useracc.9
The format of the MLINKS entries is pairwise, not MLINKS += wise. So list kernel_mount.9 the required number of times to allow make installworld to complete.
2004-12-13 23:09:19 +00:00
MLINKS+=kernel_mount.9 free_mntarg.9 \
kernel_mount.9 kernel_vmount.9 \
kernel_mount.9 mount_arg.9 \
kernel_mount.9 mount_argb.9 \
kernel_mount.9 mount_argf.9 \
kernel_mount.9 mount_argsu.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=khelp.9 khelp_add_hhook.9 \
khelp.9 KHELP_DECLARE_MOD.9 \
khelp.9 KHELP_DECLARE_MOD_UMA.9 \
khelp.9 khelp_destroy_osd.9 \
khelp.9 khelp_get_id.9 \
khelp.9 khelp_get_osd.9 \
khelp.9 khelp_init_osd.9 \
khelp.9 khelp_remove_hhook.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=kobj.9 DEFINE_CLASS.9 \
kobj.9 kobj_class_compile.9 \
kobj.9 kobj_class_compile_static.9 \
kobj.9 kobj_class_free.9 \
kobj.9 kobj_create.9 \
kobj.9 kobj_delete.9 \
As it turns out, r186347 actually is insufficient to avoid the use of the curthread-accessing part of mtx_{,un}lock(9) when using a r210623-style curthread implementation on sparc64, crashing the kernel in its early cycles as PCPU isn't set up, yet (and can't be set up as OFW is one of the things we need for that, which leads to a chicken-and-egg problem). What happens is that due to the fact that the idea of r210623 actually is to allow the compiler to cache invocations of curthread, it factors out obtaining curthread needed for both mtx_lock(9) and mtx_unlock(9) to before the branch based on kobj_mutex_inited when compiling the kernel without the debugging options. So change kobj_class_compile_static(9) to just never acquire kobj_mtx, effectively restricting it to its documented use, and add a kobj_init_static(9) for initializing objects using a class compiled with the former and that also avoids using mutex(9) (and malloc(9)). Also assert in both of these functions that they are used in their intended way only. While at it, inline kobj_register_method() and kobj_unregister_method() as there wasn't much point for factoring them out in the first place and so that a reader of the code has to figure out the locking for fewer functions missing a KOBJ_ASSERT. Tested on powerpc{,64} by andreast. Reviewed by: nwhitehorn (earlier version), jhb MFC after: 3 days
2011-11-15 20:11:03 +00:00
kobj.9 kobj_init.9 \
kobj.9 kobj_init_static.9
Doc police fixes thanks to: ru@
2007-10-26 16:50:21 +00:00
MLINKS+=kproc.9 kproc_create.9 \
kproc.9 kproc_exit.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
kproc.9 kproc_kthread_add.9 \
Fix typo: kproc_resume,.9 -> kproc_resume.9. Approved by: re (kib)
2009-07-11 17:36:59 +00:00
kproc.9 kproc_resume.9 \
Doc police fixes thanks to: ru@
2007-10-26 16:50:21 +00:00
kproc.9 kproc_shutdown.9 \
kproc.9 kproc_start.9 \
kproc.9 kproc_suspend.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
kproc.9 kproc_suspend_check.9 \
kproc.9 kthread_create.9
sort MLINKS properly Pointed out by: ru
2006-10-05 08:55:35 +00:00
MLINKS+=kqueue.9 knlist_add.9 \
add man page talking about how to interface w/ the kqueue system so others can write additional filters... mdoc police please!
2006-10-04 20:16:23 +00:00
kqueue.9 knlist_clear.9 \
kqueue.9 knlist_delete.9 \
sort MLINKS properly Pointed out by: ru
2006-10-05 08:55:35 +00:00
kqueue.9 knlist_destroy.9 \
kqueue.9 knlist_empty.9 \
kqueue.9 knlist_init.9 \
- Add knlist_init_rw_reader() function to kqueue(9). Function acquired reader lock if needed. Assert check for reader or writer lock (RA_LOCKED / RA_UNLOCKED) - While here, add knlist_init_mtx.9 to MLINKS and fix some style(9) issues Reviewed by: glebius Approved by: ae(mentor) MFC after: 2 weeks
2012-03-26 09:34:17 +00:00
kqueue.9 knlist_init_mtx.9 \
kqueue.9 knlist_init_rw_reader.9 \
sort MLINKS properly Pointed out by: ru
2006-10-05 08:55:35 +00:00
kqueue.9 knlist_remove.9 \
kqueue.9 knlist_remove_inevent.9 \
add man page talking about how to interface w/ the kqueue system so others can write additional filters... mdoc police please!
2006-10-04 20:16:23 +00:00
kqueue.9 knote_fdclose.9 \
kqueue.9 KNOTE_LOCKED.9 \
kqueue.9 KNOTE_UNLOCKED.9 \
sort MLINKS properly Pointed out by: ru
2006-10-05 08:55:35 +00:00
kqueue.9 kqfd_register.9 \
add man page talking about how to interface w/ the kqueue system so others can write additional filters... mdoc police please!
2006-10-04 20:16:23 +00:00
kqueue.9 kqueue_add_filteropts.9 \
kqueue.9 kqueue_del_filteropts.9
Doc police fixes thanks to: ru@
2007-10-26 16:50:21 +00:00
MLINKS+=kthread.9 kthread_add.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
kthread.9 kthread_exit.9 \
kthread.9 kthread_resume.9 \
Doc police fixes thanks to: ru@
2007-10-26 16:50:21 +00:00
kthread.9 kthread_shutdown.9 \
kthread.9 kthread_start.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
kthread.9 kthread_suspend.9 \
kthread.9 kthread_suspend_check.9
MLINKS+=ktr.9 CTR0.9 \
ktr.9 CTR1.9 \
ktr.9 CTR2.9 \
ktr.9 CTR3.9 \
ktr.9 CTR4.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ktr.9 CTR5.9 \
ktr.9 CTR6.9
Update manpage with lockmgr_assert() description.
2008-02-13 21:54:16 +00:00
MLINKS+=lock.9 lockdestroy.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
lock.9 lockinit.9 \
lock.9 lockmgr.9 \
Connect lockmgr_args(9) to the build.
2008-03-01 20:39:56 +00:00
lock.9 lockmgr_args.9 \
Commit manpages for lockmgr_args_rw(9) and lockmgr_rw(9).
2008-04-06 21:22:12 +00:00
lock.9 lockmgr_args_rw.9 \
Update manpage with lockmgr_assert() description.
2008-02-13 21:54:16 +00:00
lock.9 lockmgr_assert.9 \
Fix lock.9 manpage in order to recall lockmgr_disown() with 'man' command.
2008-01-22 19:58:30 +00:00
lock.9 lockmgr_disown.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
lock.9 lockmgr_printinfo.9 \
Add the newly added function lockmgr_recursed() to the manpages.
2008-01-22 20:16:09 +00:00
lock.9 lockmgr_recursed.9 \
Commit manpages for lockmgr_args_rw(9) and lockmgr_rw(9).
2008-04-06 21:22:12 +00:00
lock.9 lockmgr_rw.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
lock.9 lockstatus.9
Link the defunct MUTEX_PROFILING option to LOCK_PROFILING.
2007-05-13 22:56:58 +00:00
MLINKS+=LOCK_PROFILING.9 MUTEX_PROFILING.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=make_dev.9 destroy_dev.9 \
Add links for destroy_dev_drain, destroy_dev_sched, destroy_dev_sched_cb, make_dev_cred and make_dev_credf.
2010-08-06 16:50:48 +00:00
make_dev.9 destroy_dev_drain.9 \
make_dev.9 destroy_dev_sched.9 \
make_dev.9 destroy_dev_sched_cb.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
make_dev.9 dev_depends.9 \
Add links for destroy_dev_drain, destroy_dev_sched, destroy_dev_sched_cb, make_dev_cred and make_dev_credf.
2010-08-06 16:50:48 +00:00
make_dev.9 make_dev_alias.9 \
Add make_dev_alias_p to MLINKS. Pointed out by: pjd MFC after: 2 weeks
2011-05-05 14:13:08 +00:00
make_dev.9 make_dev_alias_p.9 \
Add links for destroy_dev_drain, destroy_dev_sched, destroy_dev_sched_cb, make_dev_cred and make_dev_credf.
2010-08-06 16:50:48 +00:00
make_dev.9 make_dev_cred.9 \
Document make_dev_p(9). Reviewed by: brueffer, kib
2010-10-24 15:56:21 +00:00
make_dev.9 make_dev_credf.9 \
Provide yet another KPI for cdev creation, make_dev_s(9). Immediate problem fixed by the new KPI is the long-standing race between device creation and assignments to cdev->si_drv1 and cdev->si_drv2, which allows the window where cdevsw methods might be called with si_drv1,2 fields not yet set. Devices typically checked for NULL and returned spurious errors to usermode, and often left some methods unchecked. The new function interface is designed to be extensible, which should allow to add more features to make_dev_s(9) without inventing yet another name for function to create devices, while maintaining KPI and even KBI backward-compatibility. Reviewed by: hps, jhb Sponsored by: The FreeBSD Foundation MFC after: 3 weeks Differential revision: https://reviews.freebsd.org/D4746
2016-01-07 20:08:02 +00:00
make_dev.9 make_dev_p.9 \
make_dev.9 make_dev_s.9
Retire the MALLOC and FREE macros. They are an abomination unto style(9). MFC after: 3 months
2008-10-23 15:53:51 +00:00
MLINKS+=malloc.9 free.9 \
Add malloc_domainset(9) and _domainset variants to other allocator KPIs. Remove malloc_domain(9) and most other _domain KPIs added in r327900. The new functions allow the caller to specify a general NUMA domain selection policy, rather than specifically requesting an allocation from a specific domain. The latter policy tends to interact poorly with M_WAITOK, resulting in situations where a caller is blocked indefinitely because the specified domain is depleted. Most existing consumers of the _domain KPIs are converted to instead use a DOMAINSET_PREF() policy, in which we fall back to other domains to satisfy the allocation request. This change also defines a set of DOMAINSET_FIXED() policies, which only permit allocations from the specified domain. Discussed with: gallatin, jeff Reported and tested by: pho (previous version) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17418
2018-10-30 18:26:34 +00:00
malloc.9 malloc_domainset.9 \
Add mallocarray.9 to malloc.9's MLINKS. X-MFC with: r327674
2018-01-11 16:41:03 +00:00
malloc.9 mallocarray.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
malloc.9 MALLOC_DECLARE.9 \
Add MLINKs for MALLOC_DEFINE and MALLOC_DECLARE. Approved by: grog (mentor)
2004-02-28 23:01:20 +00:00
malloc.9 MALLOC_DEFINE.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
malloc.9 realloc.9 \
malloc.9 reallocf.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=mbchain.9 mb_detach.9 \
mbchain.9 mb_done.9 \
mbchain.9 mb_fixhdr.9 \
mbchain.9 mb_init.9 \
mbchain.9 mb_initm.9 \
mbchain.9 mb_put_int64be.9 \
mbchain.9 mb_put_int64le.9 \
mbchain.9 mb_put_mbuf.9 \
mbchain.9 mb_put_mem.9 \
mbchain.9 mb_put_uint16be.9 \
mbchain.9 mb_put_uint16le.9 \
mbchain.9 mb_put_uint32be.9 \
mbchain.9 mb_put_uint32le.9 \
mbchain.9 mb_put_uint8.9 \
mbchain.9 mb_put_uio.9 \
mbchain.9 mb_reserve.9
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
MLINKS+=\
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_adj.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
mbuf.9 m_align.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 M_ALIGN.9 \
link mbuf to m_append so it can be found... Pointed out by: J David MFC after: 1 week
2014-01-28 23:40:02 +00:00
mbuf.9 m_append.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_apply.9 \
mbuf.9 m_cat.9 \
Document m_catpkt(), and remove misinformation about m_cat(9). Since m_cat() may copy data from the second mbuf chain into the last mbuf of the first chain, it may free the first mbuf of the second chain. Thus, the second chain is not guaranteed to be valid after m_cat() returns. Reviewed by: glebius MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D5497
2016-03-02 04:58:51 +00:00
mbuf.9 m_catpkt.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 MCHTYPE.9 \
mbuf.9 MCLGET.9 \
Add an MLINK for m_collapse. PR: 204205 Submitted by: avos MFC after: 1 week
2015-12-07 19:08:33 +00:00
mbuf.9 m_collapse.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_copyback.9 \
mbuf.9 m_copydata.9 \
mbuf.9 m_copym.9 \
mbuf.9 m_copypacket.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
mbuf.9 m_copyup.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_defrag.9 \
mbuf.9 m_devget.9 \
mbuf.9 m_dup.9 \
mbuf.9 m_dup_pkthdr.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 MEXTADD.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_fixhdr.9 \
mbuf.9 m_free.9 \
mbuf.9 m_freem.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 MGET.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_get.9 \
Document m_get2(). Reviewed by: glebius
2014-04-30 08:51:30 +00:00
mbuf.9 m_get2.9 \
document the m_getjcl function...
2013-12-20 23:57:05 +00:00
mbuf.9 m_getjcl.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_getcl.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 MGETHDR.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_gethdr.9 \
mbuf.9 m_getm.9 \
mbuf.9 m_getptr.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 MH_ALIGN.9 \
mbuf.9 M_LEADINGSPACE.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_length.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 M_MOVE_PKTHDR.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_move_pkthdr.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 M_PREPEND.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_prepend.9 \
Add m_pulldown and m_unshare to MLINKS.
2014-06-25 07:29:40 +00:00
mbuf.9 m_pulldown.9 \
add MLINKs for the mbuf.9 man page.. MFC after: 3 days
2004-09-18 19:04:24 +00:00
mbuf.9 m_pullup.9 \
mbuf.9 m_split.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 mtod.9 \
mbuf.9 M_TRAILINGSPACE.9 \
Add m_pulldown and m_unshare to MLINKS.
2014-06-25 07:29:40 +00:00
mbuf.9 m_unshare.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
mbuf.9 M_WRITABLE.9
Install symlinks for m_tag_* mbuf tag functions to the mbuf_tags.9 man page. MFC after: 1 week
2011-06-18 13:08:46 +00:00
MLINKS+=\
mbuf_tags.9 m_tag_alloc.9 \
mbuf_tags.9 m_tag_copy.9 \
mbuf_tags.9 m_tag_copy_chain.9 \
mbuf_tags.9 m_tag_delete.9 \
mbuf_tags.9 m_tag_delete_chain.9 \
mbuf_tags.9 m_tag_delete_nonpersistent.9 \
mbuf_tags.9 m_tag_find.9 \
mbuf_tags.9 m_tag_first.9 \
mbuf_tags.9 m_tag_free.9 \
mbuf_tags.9 m_tag_get.9 \
mbuf_tags.9 m_tag_init.9 \
mbuf_tags.9 m_tag_locate.9 \
mbuf_tags.9 m_tag_next.9 \
mbuf_tags.9 m_tag_prepend.9 \
mbuf_tags.9 m_tag_unlink.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=MD5.9 MD5Init.9 \
MD5.9 MD5Transform.9
MLINKS+=mdchain.9 md_append_record.9 \
mdchain.9 md_done.9 \
mdchain.9 md_get_int64.9 \
mdchain.9 md_get_int64be.9 \
mdchain.9 md_get_int64le.9 \
mdchain.9 md_get_mbuf.9 \
mdchain.9 md_get_mem.9 \
mdchain.9 md_get_uint16.9 \
mdchain.9 md_get_uint16be.9 \
mdchain.9 md_get_uint16le.9 \
mdchain.9 md_get_uint32.9 \
mdchain.9 md_get_uint32be.9 \
mdchain.9 md_get_uint32le.9 \
mdchain.9 md_get_uint8.9 \
mdchain.9 md_get_uio.9 \
mdchain.9 md_initm.9 \
mdchain.9 md_next_record.9
Bring kernel time variable and access function docs up to date by updating the list of variables and mentioning the bin(up)time functions.
2004-09-17 07:24:18 +00:00
MLINKS+=microtime.9 bintime.9 \
microtime.9 getbintime.9 \
microtime.9 getmicrotime.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
microtime.9 getnanotime.9 \
microtime.9 nanotime.9
Bring kernel time variable and access function docs up to date by updating the list of variables and mentioning the bin(up)time functions.
2004-09-17 07:24:18 +00:00
MLINKS+=microuptime.9 binuptime.9 \
microuptime.9 getbinuptime.9 \
microuptime.9 getmicrouptime.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
microuptime.9 getnanouptime.9 \
Document the sbinuptime() and getsbinuptime() functions introduced in r247452. Sponsored by: DARPA, AFRL
2013-07-25 20:53:15 +00:00
microuptime.9 getsbinuptime.9 \
microuptime.9 nanouptime.9 \
microuptime.9 sbinuptime.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=mi_switch.9 cpu_switch.9 \
mi_switch.9 cpu_throw.9
Replace CC_VAR with CCV, since the CC_VAR macro doesn't exist. While here, add MLINK for CCV.9 and DECLARE_CC_MODULE.9.
2014-12-25 15:17:57 +00:00
MLINKS+=mod_cc.9 CCV.9 \
mod_cc.9 DECLARE_CC_MODULE.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=mtx_pool.9 mtx_pool_alloc.9 \
mtx_pool.9 mtx_pool_create.9 \
mtx_pool.9 mtx_pool_destroy.9 \
mtx_pool.9 mtx_pool_find.9 \
mtx_pool.9 mtx_pool_lock.9 \
mtx_pool.9 mtx_pool_lock_spin.9 \
mtx_pool.9 mtx_pool_unlock.9 \
mtx_pool.9 mtx_pool_unlock_spin.9
MLINKS+=mutex.9 mtx_assert.9 \
mutex.9 mtx_destroy.9 \
mutex.9 mtx_init.9 \
mutex.9 mtx_initialized.9 \
mutex.9 mtx_lock.9 \
mutex.9 mtx_lock_flags.9 \
mutex.9 mtx_lock_spin.9 \
mutex.9 mtx_lock_spin_flags.9 \
mutex.9 mtx_owned.9 \
mutex.9 mtx_recursed.9 \
Allow threads to atomically release rw and sx locks while waiting for an event. Locking primitives that support this (mtx, rw, and sx) now each include their own foo_sleep() routine. - Rename msleep() to _sleep() and change it's 'struct mtx' object to a 'struct lock_object' pointer. _sleep() uses the recently added lc_unlock() and lc_lock() function pointers for the lock class of the specified lock to release the lock while the thread is suspended. - Add wrappers around _sleep() for mutexes (mtx_sleep()), rw locks (rw_sleep()), and sx locks (sx_sleep()). msleep() still exists and is now identical to mtx_sleep(), but it is deprecated. - Rename SLEEPQ_MSLEEP to SLEEPQ_SLEEP. - Rewrite much of sleep.9 to not be msleep(9) centric. - Flesh out the 'RETURN VALUES' section in sleep.9 and add an 'ERRORS' section. - Add __nonnull(1) to _sleep() and msleep_spin() so that the compiler will warn if you try to pass a NULL wait channel. The functions already have a KASSERT to that effect.
2007-03-09 22:41:01 +00:00
mutex.9 mtx_sleep.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
mutex.9 MTX_SYSINIT.9 \
mutex.9 mtx_trylock.9 \
mutex.9 mtx_trylock_flags.9 \
Implement mtx_trylock_spin(9). Discussed with: bde Reviewed by: jhb Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D7192
2016-07-23 05:30:55 +00:00
mutex.9 mtx_trylock_spin.9 \
mutex.9 mtx_trylock_spin_flags.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
mutex.9 mtx_unlock.9 \
mutex.9 mtx_unlock_flags.9 \
mutex.9 mtx_unlock_spin.9 \
mutex.9 mtx_unlock_spin_flags.9
MLINKS+=namei.9 NDFREE.9 \
Sort NDHASGIANT.9 link properly.
2010-01-19 20:36:15 +00:00
namei.9 NDINIT.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=netisr.9 netisr_clearqdrops.9 \
netisr.9 netisr_default_flow2cpu.9 \
netisr.9 netisr_dispatch.9 \
netisr.9 netisr_dispatch_src.9 \
netisr.9 netisr_get_cpucount.9 \
netisr.9 netisr_get_cpuid.9 \
netisr.9 netisr_getqdrops.9 \
netisr.9 netisr_getqlimit.9 \
netisr.9 netisr_queue.9 \
netisr.9 netisr_queue_src.9 \
netisr.9 netisr_register.9 \
netisr.9 netisr_setqlimit.9 \
netisr.9 netisr_unregister.9
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
MLINKS+=nv.9 libnv.9 \
nv.9 nvlist.9 \
nv.9 nvlist_add_binary.9 \
nv.9 nvlist_add_bool.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_add_bool_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_add_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_add_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_add_null.9 \
nv.9 nvlist_add_number.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_add_number_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_add_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_add_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_add_string.9 \
nv.9 nvlist_add_stringf.9 \
nv.9 nvlist_add_stringv.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_add_string_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_clone.9 \
nv.9 nvlist_create.9 \
nv.9 nvlist_destroy.9 \
nv.9 nvlist_dump.9 \
nv.9 nvlist_empty.9 \
nv.9 nvlist_error.9 \
nv.9 nvlist_exists.9 \
nv.9 nvlist_exists_binary.9 \
nv.9 nvlist_exists_bool.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_exists_bool_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_exists_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_exists_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_exists_null.9 \
nv.9 nvlist_exists_number.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_exists_number_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_exists_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_exists_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_exists_string.9 \
nv.9 nvlist_exists_type.9 \
nv.9 nvlist_fdump.9 \
nv.9 nvlist_flags.9 \
nv.9 nvlist_free.9 \
nv.9 nvlist_free_binary.9 \
nv.9 nvlist_free_bool.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_free_bool_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_free_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_free_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_free_null.9 \
nv.9 nvlist_free_number.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_free_number_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_free_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_free_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_free_string.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_free_string_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_free_type.9 \
nv.9 nvlist_get_binary.9 \
nv.9 nvlist_get_bool.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_get_bool_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_get_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_get_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_get_number.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_get_number_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_get_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_get_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_get_parent.9 \
nv.9 nvlist_get_string.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_get_string_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_move_binary.9 \
nv.9 nvlist_move_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_move_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_move_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_move_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_move_string.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_move_string_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_next.9 \
nv.9 nvlist_pack.9 \
nv.9 nvlist_recv.9 \
nv.9 nvlist_send.9 \
nv.9 nvlist_set_error.9 \
nv.9 nvlist_size.9 \
nv.9 nvlist_take_binary.9 \
nv.9 nvlist_take_bool.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_take_bool_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_take_descriptor.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_take_descriptor_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_take_number.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_take_number_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_take_nvlist.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_take_nvlist_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_take_string.9 \
Add missing links to the nv man page. MFC after: 1 week
2017-09-16 17:52:25 +00:00
nv.9 nvlist_take_string_array.9 \
Move nvlist documentation to the FreeBSD Kernel Developer's sections. Approved by: pjd (mentor)
2015-07-04 10:27:30 +00:00
nv.9 nvlist_unpack.9 \
nv.9 nvlist_xfer.9
[man] Add documentation for OpenFirmware API Add man pages for following OpenFirmware functions: OF_child, OF_parent, OF_peer, OF_device_from_xref, OF_device_register_xref, OF_xref_from_device, OF_getprop, OF_getencprop, OF_getencprop_alloc, OF_getprop_alloc, OF_getproplen, OF_hasprop, OF_nextprop, OF_prop_free, OF_searchencprop, OF_searchprop, OF_setprop Edited by: wblock MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D14511
2018-04-09 22:23:45 +00:00
MLINKS+=OF_child.9 OF_parent.9 \
OF_child.9 OF_peer.9
MLINKS+=OF_device_from_xref.9 OF_device_register_xref.9 \
OF_device_from_xref.9 OF_xref_from_device.9
MLINKS+=OF_getprop.9 OF_getencprop.9 \
OF_getprop.9 OF_getencprop_alloc.9 \
Document multi variants of *prop_alloc functions Add documentation and symlinks for OF_getprop_alloc_multi and OF_getencprop_alloc_multi functions. Also while here fix copy-pasted .Dt value and add one more failure condition for OF_getencprop_alloc.
2018-06-23 20:05:07 +00:00
OF_getprop.9 OF_getencprop_alloc_multi.9 \
[man] Add documentation for OpenFirmware API Add man pages for following OpenFirmware functions: OF_child, OF_parent, OF_peer, OF_device_from_xref, OF_device_register_xref, OF_xref_from_device, OF_getprop, OF_getencprop, OF_getencprop_alloc, OF_getprop_alloc, OF_getproplen, OF_hasprop, OF_nextprop, OF_prop_free, OF_searchencprop, OF_searchprop, OF_setprop Edited by: wblock MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D14511
2018-04-09 22:23:45 +00:00
OF_getprop.9 OF_getprop_alloc.9 \
Document multi variants of *prop_alloc functions Add documentation and symlinks for OF_getprop_alloc_multi and OF_getencprop_alloc_multi functions. Also while here fix copy-pasted .Dt value and add one more failure condition for OF_getencprop_alloc.
2018-06-23 20:05:07 +00:00
OF_getprop.9 OF_getprop_alloc_multi.9 \
[man] Add documentation for OpenFirmware API Add man pages for following OpenFirmware functions: OF_child, OF_parent, OF_peer, OF_device_from_xref, OF_device_register_xref, OF_xref_from_device, OF_getprop, OF_getencprop, OF_getencprop_alloc, OF_getprop_alloc, OF_getproplen, OF_hasprop, OF_nextprop, OF_prop_free, OF_searchencprop, OF_searchprop, OF_setprop Edited by: wblock MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D14511
2018-04-09 22:23:45 +00:00
OF_getprop.9 OF_getproplen.9 \
OF_getprop.9 OF_hasprop.9 \
OF_getprop.9 OF_nextprop.9 \
OF_getprop.9 OF_prop_free.9 \
OF_getprop.9 OF_searchencprop.9 \
OF_getprop.9 OF_searchprop.9 \
OF_getprop.9 OF_setprop.9
MLINKS+=OF_node_from_xref.9 OF_xref_from_node.9
Document ofw_bus_subr helpers "compatible" and "status" properties Add documentation for following functions: - ofw_bus_is_compatible - ofw_bus_is_compatible_strict - ofw_bus_node_is_compatible - ofw_bus_search_compatible - ofw_bus_get_status - ofw_bus_status_okay - ofw_bus_node_status_okay MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D14724
2018-04-08 20:53:00 +00:00
MLINKS+=ofw_bus_is_compatible.9 ofw_bus_is_compatible_strict.9 \
ofw_bus_is_compatible.9 ofw_bus_node_is_compatible.9 \
ofw_bus_is_compatible.9 ofw_bus_search_compatible.9
MLINKS+= ofw_bus_status_okay.9 ofw_bus_get_status.9 \
ofw_bus_status_okay.9 ofw_bus_node_status_okay.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=osd.9 osd_call.9 \
osd.9 osd_del.9 \
osd.9 osd_deregister.9 \
osd.9 osd_exit.9 \
osd.9 osd_get.9 \
osd.9 osd_register.9 \
osd.9 osd_set.9
Make vpanic() externally visible so that it can be called as part of the DTrace panic() action. Differential Revision: https://reviews.freebsd.org/D2349 Reviewed by: avg MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
2015-04-24 03:17:21 +00:00
MLINKS+=panic.9 vpanic.9
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
MLINKS+=PCBGROUP.9 in_pcbgroup_byhash.9 \
PCBGROUP.9 in_pcbgroup_byinpcb.9 \
PCBGROUP.9 in_pcbgroup_destroy.9 \
PCBGROUP.9 in_pcbgroup_enabled.9 \
PCBGROUP.9 in_pcbgroup_init.9 \
PCBGROUP.9 in_pcbgroup_remove.9 \
PCBGROUP.9 in_pcbgroup_update.9 \
PCBGROUP.9 in_pcbgroup_update_mbuf.9 \
PCBGROUP.9 in6_pcbgroup_byhash.9
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
MLINKS+=pci.9 pci_alloc_msi.9 \
pci.9 pci_alloc_msix.9 \
pci.9 pci_disable_busmaster.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 pci_disable_io.9 \
pci.9 pci_enable_busmaster.9 \
pci.9 pci_enable_io.9 \
pci.9 pci_find_bsf.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_find_cap.9 \
Add an MLINKS for pci_find_dbsf.9. Submitted by: ru Approved by: re (gnn)
2007-10-05 22:50:44 +00:00
pci.9 pci_find_dbsf.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 pci_find_device.9 \
Document pci_find_extcap() and pci_find_htcap().
2012-03-04 18:55:33 +00:00
pci.9 pci_find_extcap.9 \
pci.9 pci_find_htcap.9 \
Add a new helper function for PCI devices to locate the upstream PCI-express root port of a given PCI device. Reviewed by: kib, imp MFC after: 1 week Sponsored by: Chelsio Differential Revision: https://reviews.freebsd.org/D4089
2015-11-05 21:27:25 +00:00
pci.9 pci_find_pcie_root_port.9 \
Re-commit r299467 having fixed the build: Add a new get_id interface to pci and pcib. This will allow us to both detect failures, and get different PCI IDs. For the former the interface returns an int to signal an error. The ID is returned at a uintptr_t * argument. For the latter there is a type argument that allows selecting the ID type. This only specifies a single type, however a MSI type will be added to handle the need to find the ID the hardware passes to the ARM GICv3 interrupt controller. A follow up commit will be made to remove pci_get_rid. Reviewed by: jhb, rstone (previous version) Obtained from: ABT Systems Ltd Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D6239
2016-05-16 09:15:50 +00:00
pci.9 pci_get_id.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_get_max_read_req.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 pci_get_powerstate.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_get_vpd_ident.9 \
pci.9 pci_get_vpd_readonly.9 \
Document pci_iov_attach/detach in pci.9 Differential Revision: https://reviews.freebsd.org/D74 Reviewed by: bcr, wblock, emaste MFC after: 1 month Sponsored by: Sandvine Inc.
2015-03-01 00:39:55 +00:00
pci.9 pci_iov_attach.9 \
Permit the name of the /dev/iov entry to be set by the driver. The PCI_IOV option creates character devices in /dev/iov for each PF device driver that registers support for creating VFs. By default the character device is named after the PF device (e.g. /dev/iov/foo0). This change adds a variant of pci_iov_attach() called pci_iov_attach_name() that allows the name of the /dev/iov entry to be specified by the driver. Reviewed by: rstone MFC after: 1 month Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D7400
2016-08-03 17:09:12 +00:00
pci.9 pci_iov_attach_name.9 \
Document pci_iov_attach/detach in pci.9 Differential Revision: https://reviews.freebsd.org/D74 Reviewed by: bcr, wblock, emaste MFC after: 1 month Sponsored by: Sandvine Inc.
2015-03-01 00:39:55 +00:00
pci.9 pci_iov_detach.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_msi_count.9 \
pci.9 pci_msix_count.9 \
Add accessor methods to fetch the BAR holding the MSI-X table and PBA. While here, explicitly note the requirement that the BAR(s) must be allocated prior to calling pci_alloc_msix(). Reviewed by: andrew, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D4688
2015-12-23 21:51:10 +00:00
pci.9 pci_msix_pba_bar.9 \
pci.9 pci_msix_table_bar.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_pending_msix.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 pci_read_config.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_release_msi.9 \
pci.9 pci_remap_msix.9 \
Add pci_save_state() and pci_restore_state() wrappers around pci_cfg_save() and pci_cfg_restore() for device drivers to use when saving and restoring state (e.g. to handle device-specific resets). Reviewed by: imp MFC after: 2 weeks
2012-03-01 20:20:55 +00:00
pci.9 pci_restore_state.9 \
pci.9 pci_save_state.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
pci.9 pci_set_powerstate.9 \
Expand and reorganize the pci(9) manpage a bit: - Document the following routines: pci_alloc_msi(), pci_alloc_msix(), pci_find_cap(), pci_get_max_read_req(), pci_get_vpd_ident(), pci_get_vpd_readonly(), pci_msi_count(), pci_msix_count(), pci_pending_msix(), pci_release_msi(), pci_remap_msix(), and pci_set_max_read_req(). - Group the functions into five sub-sections: raw configuration access, locating devices, device information, device configuration, and message signaled interrupts. - Discourage use of pci_disable_io() and pci_enable_io() in device drivers. The PCI bus driver handles this automatically as resources are activated. MFC after: 2 weeks
2012-03-03 14:23:54 +00:00
pci.9 pci_set_max_read_req.9 \
Add helper routines for PCI device drivers to read, write, and modify PCI-Express capability registers (that is, PCI config registers in the standard PCI config space belonging to the PCI-Express capability register set). Note that all of the current PCI-e registers are either 16 or 32-bits, so only widths of 2 or 4 bytes are supported. Reviewed by: imp MFC after: 1 week Sponsored by: Chelsio Differential Revision: https://reviews.freebsd.org/D4088
2015-11-05 21:26:06 +00:00
pci.9 pci_write_config.9 \
pci.9 pcie_adjust_config.9 \
Reset PCI pass through devices via PCI-e FLR during VM start and end. Add routines to trigger a function level reset (FLR) of a PCI-express device via the PCI-express device control register. This also includes support routines to wait for pending transactions to complete as well as calculating the maximum completion timeout permitted by a device. Change the ppt(4) driver to reset pass through devices before attaching to a VM during startup and before detaching from a VM during shutdown. Reviewed by: imp, wblock (earlier version) MFC after: 1 month Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D7751
2016-09-06 21:15:35 +00:00
pci.9 pcie_flr.9 \
pci.9 pcie_max_completion_timeout.9 \
Add helper routines for PCI device drivers to read, write, and modify PCI-Express capability registers (that is, PCI config registers in the standard PCI config space belonging to the PCI-Express capability register set). Note that all of the current PCI-e registers are either 16 or 32-bits, so only widths of 2 or 4 bytes are supported. Reviewed by: imp MFC after: 1 week Sponsored by: Chelsio Differential Revision: https://reviews.freebsd.org/D4088
2015-11-05 21:26:06 +00:00
pci.9 pcie_read_config.9 \
Reset PCI pass through devices via PCI-e FLR during VM start and end. Add routines to trigger a function level reset (FLR) of a PCI-express device via the PCI-express device control register. This also includes support routines to wait for pending transactions to complete as well as calculating the maximum completion timeout permitted by a device. Change the ppt(4) driver to reset pass through devices before attaching to a VM during startup and before detaching from a VM during shutdown. Reviewed by: imp, wblock (earlier version) MFC after: 1 month Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D7751
2016-09-06 21:15:35 +00:00
pci.9 pcie_wait_for_pending_transactions.9 \
remove \, it confuses things.
2015-11-05 22:50:21 +00:00
pci.9 pcie_write_config.9
Document the interface for defining a configuration schema Differential Revision: https://reviews.freebsd.org/D89 Reviewed by: wblock, emaste, allanjude MFC after: 1 month Sponsored by: Sandvine Inc.
2015-03-01 00:59:21 +00:00
MLINKS+=pci_iov_schema.9 pci_iov_schema_alloc_node.9 \
pci_iov_schema.9 pci_iov_schema_add_bool.9 \
pci_iov_schema.9 pci_iov_schema_add_string.9 \
pci_iov_schema.9 pci_iov_schema_add_uint8.9 \
pci_iov_schema.9 pci_iov_schema_add_uint16.9 \
pci_iov_schema.9 pci_iov_schema_add_uint32.9 \
pci_iov_schema.9 pci_iov_schema_add_uint64.9 \
pci_iov_schema.9 pci_iov_schema_add_unicast_mac.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=pfil.9 pfil_add_hook.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
pfil.9 pfil_head_register.9 \
pfil.9 pfil_head_unregister.9 \
pfil.9 pfil_remove_hook.9 \
pfil.9 pfil_run_hooks.9 \
New pfil(9) KPI together with newborn pfil API and control utility. The KPI have been reviewed and cleansed of features that were planned back 20 years ago and never implemented. The pfil(9) internals have been made opaque to protocols with only returned types and function declarations exposed. The KPI is made more strict, but at the same time more extensible, as kernel uses same command structures that userland ioctl uses. In nutshell [KA]PI is about declaring filtering points, declaring filters and linking and unlinking them together. New [KA]PI makes it possible to reconfigure pfil(9) configuration: change order of hooks, rehook filter from one filtering point to a different one, disconnect a hook on output leaving it on input only, prepend/append a filter to existing list of filters. Now it possible for a single packet filter to provide multiple rulesets that may be linked to different points. Think of per-interface ACLs in Cisco or Juniper. None of existing packet filters yet support that, however limited usage is already possible, e.g. default ruleset can be moved to single interface, as soon as interface would pride their filtering points. Another future feature is possiblity to create pfil heads, that provide not an mbuf pointer but just a memory pointer with length. That would allow filtering at very early stages of a packet lifecycle, e.g. when packet has just been received by a NIC and no mbuf was yet allocated. Differential Revision: https://reviews.freebsd.org/D18951
2019-01-31 23:01:03 +00:00
pfil.9 pfil_link.9
Manpage for pfind() and zpfind(). Submitted by: Evan Sarmiento <kaworu@sektor7.ath.cx>
2001-07-16 07:04:09 +00:00
MLINKS+=pfind.9 zpfind.9
Add a manual page for PHOLD() and friends. MFC after: 1 week
2015-11-08 01:41:44 +00:00
MLINKS+=PHOLD.9 PRELE.9 \
PHOLD.9 _PHOLD.9 \
PHOLD.9 _PRELE.9 \
PHOLD.9 PROC_ASSERT_HELD.9 \
PHOLD.9 PROC_ASSERT_NOT_HELD.9
Add manual page documentation for the machine-independent PMAP subsystem. Include documentation of alc's new pmap_extract_and_hold() function. Reviewed by: hmp Approved by: jake (mentor)
2003-09-25 19:14:40 +00:00
MLINKS+=pmap_copy.9 pmap_copy_page.9
MLINKS+=pmap_extract.9 pmap_extract_and_hold.9
MLINKS+=pmap_init.9 pmap_init2.9
Correct the name of the man page for pmap_ts_referenced(). Sponsored by: EMC / Isilon Storage Division
2014-07-16 23:17:57 +00:00
MLINKS+=pmap_is_modified.9 pmap_ts_referenced.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=pmap_pinit.9 pmap_pinit0.9 \
pmap_pinit.9 pmap_pinit2.9
Add manual page documentation for the machine-independent PMAP subsystem. Include documentation of alc's new pmap_extract_and_hold() function. Reviewed by: hmp Approved by: jake (mentor)
2003-09-25 19:14:40 +00:00
MLINKS+=pmap_qenter.9 pmap_qremove.9
Create man page for pmap_quick_enter_page(9) and pmap_quick_remove_page(9) Reviewed by: kib, brueffer, wblock Approved by: kib (mentor) Differential Revision: https://reviews.freebsd.org/D3312
2015-08-07 12:13:15 +00:00
MLINKS+=pmap_quick_enter_page.9 pmap_quick_remove_page.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=pmap_remove.9 pmap_remove_all.9 \
pmap_remove.9 pmap_remove_pages.9
Add pmap_wired_count() and pmap_resident_count() to the pmap documentation. Discussed with: peter
2003-10-06 01:49:35 +00:00
MLINKS+=pmap_resident_count.9 pmap_wired_count.9
Remove support for idle page zeroing. Idle page zeroing has been disabled by default on all architectures since r170816 and has some bugs that make it seemingly unusable. Specifically, the idle-priority pagezero thread exacerbates contention for the free page lock, and yields the CPU without releasing it in non-preemptive kernels. The pagezero thread also does not behave correctly when superpage reservations are enabled: its target is a function of v_free_count, which includes reserved-but-free pages, but it is only able to zero pages belonging to the physical memory allocator. Reviewed by: alc, imp, kib Differential Revision: https://reviews.freebsd.org/D7714
2016-09-03 20:38:13 +00:00
MLINKS+=pmap_zero_page.9 pmap_zero_area.9
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
MLINKS+=printf.9 log.9 \
printf.9 tprintf.9 \
printf.9 uprintf.9
o Actually add MLINKs for priv(9) functions.
2007-03-28 04:41:50 +00:00
MLINKS+=priv.9 priv_check.9 \
o Trim unneeded backslash.
2007-03-28 04:43:55 +00:00
priv.9 priv_check_cred.9
Add prng(9) API Add prng(9) as a replacement for random(9) in the kernel. There are two major differences from random(9) and random(3): - General prng(9) APIs (prng32(9), etc) do not guarantee an implementation or particular sequence; they should not be used for repeatable simulations. - However, specific named API families are also exposed (for now: PCG), and those are expected to be repeatable (when so-guaranteed by the named algorithm). Some minor differences from random(3) and earlier random(9): - PRNG state for the general prng(9) APIs is per-CPU; this eliminates contention on PRNG state in SMP workloads. Each PCPU generator in an SMP system produces a unique sequence. - Better statistical properties than the Park-Miller ("minstd") PRNG (longer period, uniform distribution in all bits, passes BigCrush/PractRand analysis). - Faster than Park-Miller ("minstd") PRNG -- no division is required to step PCG-family PRNGs. For now, random(9) becomes a thin shim around prng32(). Eventually I would like to mechanically switch consumers over to the explicit API. Reviewed by: kib, markj (previous version both) Discussed with: markm Differential Revision: https://reviews.freebsd.org/D25916
2020-08-13 20:48:14 +00:00
MLINKS+=prng.9 prng32.9 \
prng.9 prng32_bounded.9 \
prng.9 prng64.9 \
prng.9 prng64_bounded.9
Add helper functions proc_readmem() and proc_writemem(). These helper functions can be used to read in or write a buffer from or to an arbitrary process' address space. Without them, this can only be done using proc_rwmem(), which requires the caller to fill out a uio. This is onerous and results in code duplication; the new functions provide a simpler interface which is sufficient for most existing callers of proc_rwmem(). This change also adds a manual page for proc_rwmem() and the new functions. Reviewed by: jhb, kib Differential Revision: https://reviews.freebsd.org/D4245
2015-12-07 21:33:15 +00:00
MLINKS+=proc_rwmem.9 proc_readmem.9 \
proc_rwmem.9 proc_writemem.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=psignal.9 gsignal.9 \
Mention tdsignal(9). MFC after: 1 week
2011-10-07 22:14:18 +00:00
psignal.9 pgsignal.9 \
psignal.9 tdsignal.9
Catch up with recent changes in pwmbus(9). The pwm(9) and pwmbus(9) interfaces were unified into pwmbus(9), and the PWMBUS_CHANNEL_MAX method was renamed PWMBUS_CHANNEL_COUNT. The pwmbus_attach_bus() function just went away completely. Also, fix a few typos such as s/is/if/.
2019-06-21 14:46:43 +00:00
MLINKS+=pwmbus.9 pwm.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=random.9 arc4rand.9 \
random.9 arc4random.9 \
random(4): Add is_random_seeded(9) KPI The imagined use is for early boot consumers of random to be able to make decisions based on whether random is available yet or not. One such consumer seems to be __stack_chk_init(), which runs immediately after random is initialized. A follow-up patch will attempt to address that. Reported by: many Reviewed by: delphij (except man page) Approved by: secteam(delphij) Differential Revision: https://reviews.freebsd.org/D19926
2019-04-16 17:12:17 +00:00
random.9 is_random_seeded.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
random.9 read_random.9 \
Implement the CloudABI random_get() system call. The random_get() system call works similar to getentropy()/getrandom() on OpenBSD/Linux. It fills a buffer with random data. This change introduces a new function, read_random_uio(), that is used to implement read() on the random devices. We can call into this function from within the CloudABI compatibility layer. Approved by: secteam Reviewed by: jmg, markm, wblock Obtained from: https://github.com/NuxiNL/freebsd Differential Revision: https://reviews.freebsd.org/D3053
2015-07-14 18:45:15 +00:00
random.9 read_random_uio.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
random.9 srandom.9
add missing MLINKS for functions that this man page documents. This page should be renamed to eliminate an unneeded inode. Forgotten by: markm
2017-03-05 18:37:25 +00:00
MLINKS+=random_harvest.9 random_harvest_direct.9 \
random_harvest.9 random_harvest_fast.9 \
random_harvest.9 random_harvest_queue.9
Add a man page for ratecheck(9) and ppsratecheck(9).
2018-08-17 17:16:38 +00:00
MLINKS+=ratecheck.9 ppsratecheck.9
Add a simple manage for the refcount(9) API. Requested by: rwatson
2009-03-30 18:01:12 +00:00
MLINKS+=refcount.9 refcount_acquire.9 \
refcount.9 refcount_init.9 \
refcount.9 refcount_release.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=resource_int_value.9 resource_long_value.9 \
resource_int_value.9 resource_string_value.9
MLINKS+=rman.9 rman_activate_resource.9 \
Extend the rman(9) API to support altering an existing resource. Specifically, these changes allow a resource to back a relocatable and resizable resource such as the I/O window decoders in PCI-PCI bridges. - rman_adjust_resource() can adjust the start and end address of an existing resource. It only succeeds if the newly requested address space is already free. It also supports shrinking a resource in which case the freed space will be marked unallocated in the rman. - rman_first_free_region() and rman_last_free_region() return the start and end addresses for the first or last unallocated region in an rman, respectively. This can be used to determine by how much the resource backing an rman must be adjusted to accomodate an allocation request that does not fit into the existing rman. While here, document the rm_start and rm_end fields in struct rman, rman_is_region_manager(), the bound argument to rman_reserve_resource_bound(), and rman_init_from_resource().
2011-04-29 20:05:19 +00:00
rman.9 rman_adjust_resource.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_deactivate_resource.9 \
rman.9 rman_fini.9 \
Extend the rman(9) API to support altering an existing resource. Specifically, these changes allow a resource to back a relocatable and resizable resource such as the I/O window decoders in PCI-PCI bridges. - rman_adjust_resource() can adjust the start and end address of an existing resource. It only succeeds if the newly requested address space is already free. It also supports shrinking a resource in which case the freed space will be marked unallocated in the rman. - rman_first_free_region() and rman_last_free_region() return the start and end addresses for the first or last unallocated region in an rman, respectively. This can be used to determine by how much the resource backing an rman must be adjusted to accomodate an allocation request that does not fit into the existing rman. While here, document the rm_start and rm_end fields in struct rman, rman_is_region_manager(), the bound argument to rman_reserve_resource_bound(), and rman_init_from_resource().
2011-04-29 20:05:19 +00:00
rman.9 rman_first_free_region.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_get_bushandle.9 \
rman.9 rman_get_bustag.9 \
Add rman_get_device(9) to SYNOPSIS, .Nm and MLINK it to rman(9).
2004-05-17 21:25:02 +00:00
rman.9 rman_get_device.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_get_end.9 \
rman.9 rman_get_flags.9 \
Add new bus methods for mapping resources. Add a pair of bus methods that can be used to "map" resources for direct CPU access using bus_space(9). bus_map_resource() creates a mapping and bus_unmap_resource() releases a previously created mapping. Mappings are described by 'struct resource_map' object. Pointers to these objects can be passed as the first argument to the bus_space wrapper API used for bus resources. Drivers that wish to map all of a resource using default settings (for example, using uncacheable memory attributes) do not need to change. However, drivers that wish to use non-default settings can now do so without jumping through hoops. First, an RF_UNMAPPED flag is added to request that a resource is not implicitly mapped with the default settings when it is activated. This permits other activation steps (such as enabling I/O or memory decoding in a device's PCI command register) to be taken without creating a mapping. Right now the AGP drivers don't set RF_ACTIVE to avoid using up a large amount of KVA to map the AGP aperture on 32-bit platforms. Once RF_UNMAPPED is supported on all platforms that support AGP this can be changed to using RF_UNMAPPED with RF_ACTIVE instead. Second, bus_map_resource accepts an optional structure that defines additional settings for a given mapping. For example, a driver can now request to map only a subset of a resource instead of the entire range. The AGP driver could also use this to only map the first page of the aperture (IIRC, it calls pmap_mapdev() directly to map the first page currently). I will also eventually change the PCI-PCI bridge driver to request mappings of the subset of the I/O window resource on its parent side to create mappings for child devices rather than passing child resources directly up to nexus to be mapped. This also permits bridges that do address translation to request suitable mappings from a resource on the "upper" side of the bus when mapping resources on the "lower" side of the bus. Another attribute that can be specified is an alternate memory attribute for memory-mapped resources. This can be used to request a Write-Combining mapping of a PCI BAR in an MI fashion. (Currently the drivers that do this call pmap_change_attr() directly for x86 only.) Note that this commit only adds the MI framework. Each platform needs to add support for handling RF_UNMAPPED and thew new bus_map/unmap_resource methods. Generally speaking, any drivers that are calling rman_set_bustag() and rman_set_bushandle() need to be updated. Discussed on: arch Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D5237
2016-05-20 17:57:47 +00:00
rman.9 rman_get_mapping.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_get_rid.9 \
rman.9 rman_get_size.9 \
rman.9 rman_get_start.9 \
rman.9 rman_get_virtual.9 \
rman.9 rman_init.9 \
Extend the rman(9) API to support altering an existing resource. Specifically, these changes allow a resource to back a relocatable and resizable resource such as the I/O window decoders in PCI-PCI bridges. - rman_adjust_resource() can adjust the start and end address of an existing resource. It only succeeds if the newly requested address space is already free. It also supports shrinking a resource in which case the freed space will be marked unallocated in the rman. - rman_first_free_region() and rman_last_free_region() return the start and end addresses for the first or last unallocated region in an rman, respectively. This can be used to determine by how much the resource backing an rman must be adjusted to accomodate an allocation request that does not fit into the existing rman. While here, document the rm_start and rm_end fields in struct rman, rman_is_region_manager(), the bound argument to rman_reserve_resource_bound(), and rman_init_from_resource().
2011-04-29 20:05:19 +00:00
rman.9 rman_init_from_resource.9 \
rman.9 rman_is_region_manager.9 \
rman.9 rman_last_free_region.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_make_alignment_flags.9 \
rman.9 rman_manage_region.9 \
rman.9 rman_release_resource.9 \
rman.9 rman_reserve_resource.9 \
rman.9 rman_reserve_resource_bound.9 \
rman.9 rman_set_bushandle.9 \
rman.9 rman_set_bustag.9 \
Add new bus methods for mapping resources. Add a pair of bus methods that can be used to "map" resources for direct CPU access using bus_space(9). bus_map_resource() creates a mapping and bus_unmap_resource() releases a previously created mapping. Mappings are described by 'struct resource_map' object. Pointers to these objects can be passed as the first argument to the bus_space wrapper API used for bus resources. Drivers that wish to map all of a resource using default settings (for example, using uncacheable memory attributes) do not need to change. However, drivers that wish to use non-default settings can now do so without jumping through hoops. First, an RF_UNMAPPED flag is added to request that a resource is not implicitly mapped with the default settings when it is activated. This permits other activation steps (such as enabling I/O or memory decoding in a device's PCI command register) to be taken without creating a mapping. Right now the AGP drivers don't set RF_ACTIVE to avoid using up a large amount of KVA to map the AGP aperture on 32-bit platforms. Once RF_UNMAPPED is supported on all platforms that support AGP this can be changed to using RF_UNMAPPED with RF_ACTIVE instead. Second, bus_map_resource accepts an optional structure that defines additional settings for a given mapping. For example, a driver can now request to map only a subset of a resource instead of the entire range. The AGP driver could also use this to only map the first page of the aperture (IIRC, it calls pmap_mapdev() directly to map the first page currently). I will also eventually change the PCI-PCI bridge driver to request mappings of the subset of the I/O window resource on its parent side to create mappings for child devices rather than passing child resources directly up to nexus to be mapped. This also permits bridges that do address translation to request suitable mappings from a resource on the "upper" side of the bus when mapping resources on the "lower" side of the bus. Another attribute that can be specified is an alternate memory attribute for memory-mapped resources. This can be used to request a Write-Combining mapping of a PCI BAR in an MI fashion. (Currently the drivers that do this call pmap_change_attr() directly for x86 only.) Note that this commit only adds the MI framework. Each platform needs to add support for handling RF_UNMAPPED and thew new bus_map/unmap_resource methods. Generally speaking, any drivers that are calling rman_set_bustag() and rman_set_bushandle() need to be updated. Discussed on: arch Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D5237
2016-05-20 17:57:47 +00:00
rman.9 rman_set_mapping.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
rman.9 rman_set_rid.9 \
rman.9 rman_set_virtual.9
Several improvements to rmlock(9). Many of these are based on patches provided by Isilon. - Add an rm_assert() supporting various lock assertions similar to other locking primitives. Because rmlocks track readers the assertions are always fully accurate unlike rw_assert() and sx_assert(). - Flesh out the lock class methods for rmlocks to support sleeping via condvars and rm_sleep() (but only while holding write locks), rmlock details in 'show lock' in DDB, and the lc_owner method used by dtrace. - Add an internal destroyed cookie so that API functions can assert that an rmlock is not destroyed. - Make use of rm_assert() to add various assertions to the API (e.g. to assert locks are held when an unlock routine is called). - Give RM_SLEEPABLE locks their own lock class and always use the rmlock's own lock_object with WITNESS. - Use THREAD_NO_SLEEPING() / THREAD_SLEEPING_OK() to disallow sleeping while holding a read lock on an rmlock. Submitted by: andre Obtained from: EMC/Isilon
2013-06-25 18:44:15 +00:00
MLINKS+=rmlock.9 rm_assert.9 \
rmlock.9 rm_destroy.9 \
Hook up rmlock(9) and its links to the build.
2007-11-10 16:47:38 +00:00
rmlock.9 rm_init.9 \
Several improvements to rmlock(9). Many of these are based on patches provided by Isilon. - Add an rm_assert() supporting various lock assertions similar to other locking primitives. Because rmlocks track readers the assertions are always fully accurate unlike rw_assert() and sx_assert(). - Flesh out the lock class methods for rmlocks to support sleeping via condvars and rm_sleep() (but only while holding write locks), rmlock details in 'show lock' in DDB, and the lc_owner method used by dtrace. - Add an internal destroyed cookie so that API functions can assert that an rmlock is not destroyed. - Make use of rm_assert() to add various assertions to the API (e.g. to assert locks are held when an unlock routine is called). - Give RM_SLEEPABLE locks their own lock class and always use the rmlock's own lock_object with WITNESS. - Use THREAD_NO_SLEEPING() / THREAD_SLEEPING_OK() to disallow sleeping while holding a read lock on an rmlock. Submitted by: andre Obtained from: EMC/Isilon
2013-06-25 18:44:15 +00:00
rmlock.9 rm_init_flags.9 \
Hook up rmlock(9) and its links to the build.
2007-11-10 16:47:38 +00:00
rmlock.9 rm_rlock.9 \
rmlock.9 rm_runlock.9 \
Several improvements to rmlock(9). Many of these are based on patches provided by Isilon. - Add an rm_assert() supporting various lock assertions similar to other locking primitives. Because rmlocks track readers the assertions are always fully accurate unlike rw_assert() and sx_assert(). - Flesh out the lock class methods for rmlocks to support sleeping via condvars and rm_sleep() (but only while holding write locks), rmlock details in 'show lock' in DDB, and the lc_owner method used by dtrace. - Add an internal destroyed cookie so that API functions can assert that an rmlock is not destroyed. - Make use of rm_assert() to add various assertions to the API (e.g. to assert locks are held when an unlock routine is called). - Give RM_SLEEPABLE locks their own lock class and always use the rmlock's own lock_object with WITNESS. - Use THREAD_NO_SLEEPING() / THREAD_SLEEPING_OK() to disallow sleeping while holding a read lock on an rmlock. Submitted by: andre Obtained from: EMC/Isilon
2013-06-25 18:44:15 +00:00
rmlock.9 rm_sleep.9 \
Hook up rmlock(9) and its links to the build.
2007-11-10 16:47:38 +00:00
rmlock.9 RM_SYSINIT.9 \
Clean up the SYSINIT_FLAGS definitions for rwlock(9) and rmlock(9). Avoid duplication in their macro definitions, and document them. No functional change intended. MFC after: 1 week
2017-11-21 14:59:23 +00:00
rmlock.9 RM_SYSINIT_FLAGS.9 \
Several improvements to rmlock(9). Many of these are based on patches provided by Isilon. - Add an rm_assert() supporting various lock assertions similar to other locking primitives. Because rmlocks track readers the assertions are always fully accurate unlike rw_assert() and sx_assert(). - Flesh out the lock class methods for rmlocks to support sleeping via condvars and rm_sleep() (but only while holding write locks), rmlock details in 'show lock' in DDB, and the lc_owner method used by dtrace. - Add an internal destroyed cookie so that API functions can assert that an rmlock is not destroyed. - Make use of rm_assert() to add various assertions to the API (e.g. to assert locks are held when an unlock routine is called). - Give RM_SLEEPABLE locks their own lock class and always use the rmlock's own lock_object with WITNESS. - Use THREAD_NO_SLEEPING() / THREAD_SLEEPING_OK() to disallow sleeping while holding a read lock on an rmlock. Submitted by: andre Obtained from: EMC/Isilon
2013-06-25 18:44:15 +00:00
rmlock.9 rm_try_rlock.9 \
Hook up rmlock(9) and its links to the build.
2007-11-10 16:47:38 +00:00
rmlock.9 rm_wlock.9 \
rmlock.9 rm_wowned.9 \
rmlock.9 rm_wunlock.9
Sort.
2007-11-13 20:26:27 +00:00
MLINKS+=rtalloc.9 rtalloc1.9 \
rtalloc.9 rtalloc_ign.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
rtalloc.9 RT_ADDREF.9 \
rtalloc.9 RT_LOCK.9 \
rtalloc.9 RT_REMREF.9 \
rtalloc.9 RT_RTFREE.9 \
rtalloc.9 RT_UNLOCK.9 \
More MLINKS for rtalloc.9
2011-12-14 14:55:19 +00:00
rtalloc.9 RTFREE_LOCKED.9 \
Sort.
2007-11-13 20:26:27 +00:00
rtalloc.9 RTFREE.9 \
More MLINKS for rtalloc.9
2011-12-14 14:55:19 +00:00
rtalloc.9 rtfree.9 \
rtalloc.9 rtalloc1_fib.9 \
rtalloc.9 rtalloc_ign_fib.9 \
rtalloc.9 rtalloc_fib.9
Tie up some loose ends r88509 left behind: - chooseproc() is long gone, MLINK choosethread instead - Update NAME section for choosethread - Mark chooseproc.9 for removal PR: 149549 Submitted by: pluknet MFC after: 1 week
2010-08-15 21:25:52 +00:00
MLINKS+=runqueue.9 choosethread.9 \
Sort.
2007-11-13 20:26:27 +00:00
runqueue.9 procrunnable.9 \
runqueue.9 remrunqueue.9 \
runqueue.9 setrunqueue.9
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
MLINKS+=rwlock.9 rw_assert.9 \
rwlock.9 rw_destroy.9 \
rwlock.9 rw_downgrade.9 \
rwlock.9 rw_init.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
rwlock.9 rw_init_flags.9 \
- Sort rwlock functions similar to the order in mutex(9). - Add a missing MLINK.
2007-03-09 16:44:58 +00:00
rwlock.9 rw_initialized.9 \
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
rwlock.9 rw_rlock.9 \
rwlock.9 rw_runlock.9 \
Add link for rw_unlock(9) to rwlock(9). MFC after: 3 days Sponsored by: EMC / Isilon Storage Division
2015-08-20 18:22:06 +00:00
rwlock.9 rw_unlock.9 \
Allow threads to atomically release rw and sx locks while waiting for an event. Locking primitives that support this (mtx, rw, and sx) now each include their own foo_sleep() routine. - Rename msleep() to _sleep() and change it's 'struct mtx' object to a 'struct lock_object' pointer. _sleep() uses the recently added lc_unlock() and lc_lock() function pointers for the lock class of the specified lock to release the lock while the thread is suspended. - Add wrappers around _sleep() for mutexes (mtx_sleep()), rw locks (rw_sleep()), and sx locks (sx_sleep()). msleep() still exists and is now identical to mtx_sleep(), but it is deprecated. - Rename SLEEPQ_MSLEEP to SLEEPQ_SLEEP. - Rewrite much of sleep.9 to not be msleep(9) centric. - Flesh out the 'RETURN VALUES' section in sleep.9 and add an 'ERRORS' section. - Add __nonnull(1) to _sleep() and msleep_spin() so that the compiler will warn if you try to pass a NULL wait channel. The functions already have a KASSERT to that effect.
2007-03-09 22:41:01 +00:00
rwlock.9 rw_sleep.9 \
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
rwlock.9 RW_SYSINIT.9 \
Clean up the SYSINIT_FLAGS definitions for rwlock(9) and rmlock(9). Avoid duplication in their macro definitions, and document them. No functional change intended. MFC after: 1 week
2017-11-21 14:59:23 +00:00
rwlock.9 RW_SYSINIT_FLAGS.9 \
Add manpages for rw_try_rlock() and rw_try_wlock() functions.
2008-04-01 20:56:45 +00:00
rwlock.9 rw_try_rlock.9 \
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
rwlock.9 rw_try_upgrade.9 \
Add manpages for rw_try_rlock() and rw_try_wlock() functions.
2008-04-01 20:56:45 +00:00
rwlock.9 rw_try_wlock.9 \
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
rwlock.9 rw_wlock.9 \
Add rw_wowned(9) symlink.
2007-02-26 19:09:36 +00:00
rwlock.9 rw_wowned.9 \
Add MLINKS for rwlock(9).
2006-04-19 21:09:39 +00:00
rwlock.9 rw_wunlock.9
Add missing links. MFC after: 2 weeks
2005-04-15 10:57:34 +00:00
MLINKS+=sbuf.9 sbuf_bcat.9 \
sbuf.9 sbuf_bcopyin.9 \
sbuf.9 sbuf_bcpy.9 \
sbuf.9 sbuf_cat.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_clear.9 \
sbuf(9): add MLINKS for sbuf_{clear,get,set}_flags(9) These functions were added in r279992. MFC after: 2 months Sponsored by: Dell EMC Isilon
2017-04-06 05:02:03 +00:00
sbuf.9 sbuf_clear_flags.9 \
Add missing links. MFC after: 2 weeks
2005-04-15 10:57:34 +00:00
sbuf.9 sbuf_copyin.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_cpy.9 \
sbuf.9 sbuf_data.9 \
sbuf.9 sbuf_delete.9 \
Add missing links. MFC after: 2 weeks
2005-04-15 10:57:34 +00:00
sbuf.9 sbuf_done.9 \
Replace sbuf_overflowed() with sbuf_error(), which returns any error code associated with overflow or with the drain function. While this function is not expected to be used often, it produces more information in the form of an errno that sbuf_overflowed() did.
2010-09-10 16:42:16 +00:00
sbuf.9 sbuf_error.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_finish.9 \
sbuf(9): add MLINKS for sbuf_{clear,get,set}_flags(9) These functions were added in r279992. MFC after: 2 months Sponsored by: Dell EMC Isilon
2017-04-06 05:02:03 +00:00
sbuf.9 sbuf_get_flags.9 \
Correct MLINKS for sbuf_hexdump(9) sbuf_hexdump(9) should be linked to sbuf(9), not hexdump(3). Another review will be posted to deduplicate the sbuf_hexdump reference in in hexdump(3) or at the very least make the information less duplicative. MFC after: 1 week X-MFC with: r313437 Sponsored by: Dell EMC Isilon
2017-03-03 06:31:47 +00:00
sbuf.9 sbuf_hexdump.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_len.9 \
sbuf.9 sbuf_new.9 \
Add missing symlinks for the sbuf man page
2013-10-23 03:27:42 +00:00
sbuf.9 sbuf_new_auto.9 \
Document sbuf_new_for_sysctl(9). Pointed out by: lstewart
2011-01-25 17:39:52 +00:00
sbuf.9 sbuf_new_for_sysctl.9 \
Follow r350693 to add a link for sbuf_nl_terminate(9) Sponsored by: The FreeBSD Foundation
2019-08-08 00:51:17 +00:00
sbuf.9 sbuf_nl_terminate.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_printf.9 \
device_printf: Use sbuf for more coherent prints on SMP device_printf does multiple calls to printf allowing other console messages to be inserted between the device name, and the rest of the message. This change uses sbuf to compose to two into a single buffer, and prints it all at once. It exposes an sbuf drain function (drain-to-printf) for common use. Update documentation to match; some unit tests included. Submitted by: jmg Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D16690
2019-05-07 17:47:20 +00:00
sbuf.9 sbuf_printf_drain.9 \
sbuf.9 sbuf_putbuf.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_putc.9 \
Add drain functionality to sbufs. The drain is a function that is called when the sbuf internal buffer is filled. For kernel sbufs with a drain, the internal buffer will never be expanded. For userland sbufs with a drain, the internal buffer may still be expanded by sbuf_[v]printf(3). Sbufs now have three basic uses: 1) static string manipulation. Overflow is marked. 2) dynamic string manipulation. Overflow triggers string growth. 3) drained string manipulation. Overflow triggers draining. In all cases the manipulation is 'safe' in that overflow is detected and managed. Reviewed by: phk (the previous version)
2010-09-09 17:49:18 +00:00
sbuf.9 sbuf_set_drain.9 \
sbuf(9): add MLINKS for sbuf_{clear,get,set}_flags(9) These functions were added in r279992. MFC after: 2 months Sponsored by: Dell EMC Isilon
2017-04-06 05:02:03 +00:00
sbuf.9 sbuf_set_flags.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_setpos.9 \
Add missing symlinks for the sbuf man page
2013-10-23 03:27:42 +00:00
sbuf.9 sbuf_start_section.9 \
sbuf.9 sbuf_end_section.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sbuf.9 sbuf_trim.9 \
sbuf.9 sbuf_vprintf.9
MLINKS+=scheduler.9 curpriority_cmp.9 \
scheduler.9 maybe_resched.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
scheduler.9 propagate_priority.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
scheduler.9 resetpriority.9 \
scheduler.9 roundrobin.9 \
scheduler.9 roundrobin_interval.9 \
scheduler.9 schedclock.9 \
scheduler.9 schedcpu.9 \
scheduler.9 sched_setup.9 \
scheduler.9 setrunnable.9 \
scheduler.9 updatepri.9
Add a man page for the SDT_* macros, which can be used to define new static DTrace probes and providers in kernel code. MFC after: 1 week
2013-07-06 20:31:22 +00:00
MLINKS+=SDT.9 SDT_PROVIDER_DECLARE.9 \
SDT.9 SDT_PROVIDER_DEFINE.9 \
SDT.9 SDT_PROBE_DECLARE.9 \
SDT.9 SDT_PROBE_DEFINE.9 \
SDT.9 SDT_PROBE.9
Document kernel functions securelevel_gt and securelevel_ge. Approved by: simon(mentor) Submitted by: Christian S.J. Peron <maneo@bsdpro.com> PR: docs/62331 mdoc(7) cleanup by: ru
2004-03-07 15:22:08 +00:00
MLINKS+=securelevel_gt.9 securelevel_ge.9
Fix an error in the generation of the manpage after r225177. Sponsored by: Sandvine Incorporated Submitted by: jkim Approved by: re (bz) MFC after: 3 weeks X-MFC: r225177
2011-08-25 17:42:27 +00:00
MLINKS+=selrecord.9 seldrain.9 \
selrecord.9 selwakeup.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=sema.9 sema_destroy.9 \
sema.9 sema_init.9 \
sema.9 sema_post.9 \
sema.9 sema_timedwait.9 \
sema.9 sema_trywait.9 \
sema.9 sema_value.9 \
sema.9 sema_wait.9
seqc: add man page Reviewed by: markj Earlier version reviewed by: emaste, mjg, bcr, 0mp Differential Revision: https://reviews.freebsd.org/D16744
2019-07-29 21:53:02 +00:00
MLINKS+=seqc.9 seqc_consistent.9 \
seqc.9 seqc_read.9 \
seqc.9 seqc_write_begin.9 \
seqc.9 seqc_write_end.9
Add MLINKS for sf_buf.9.
2007-01-29 11:27:44 +00:00
MLINKS+=sf_buf.9 sf_buf_alloc.9 \
sf_buf.9 sf_buf_free.9 \
sf_buf.9 sf_buf_kva.9 \
sf_buf.9 sf_buf_page.9
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
MLINKS+=sglist.9 sglist_alloc.9 \
sglist.9 sglist_append.9 \
Add sglist_append_bio(9) to append a struct bio's data to a sglist Reviewed by: jhb, kib (long ago)
2014-01-13 04:41:08 +00:00
sglist.9 sglist_append_bio.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 sglist_append_mbuf.9 \
Fixup for r360574: install new mlinks for sglist(9) and remove old ones.
2020-07-07 02:41:51 +00:00
sglist.9 sglist_append_mbuf_epg.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 sglist_append_phys.9 \
Add sglist_append_sglist(). This function permits a range of one scatter/gather list to be appended to another sglist. This can be used to construct a scatter/gather list that reorders or duplicates ranges from one or more existing scatter/gather lists. Sponsored by: Chelsio Communications
2017-05-16 23:31:52 +00:00
sglist.9 sglist_append_sglist.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 sglist_append_uio.9 \
sglist.9 sglist_append_user.9 \
Add sglist functions for working with arrays of VM pages. sglist_count_vmpages() determines the number of segments required for a buffer described by an array of VM pages. sglist_append_vmpages() adds the segments described by such a buffer to an sglist. The latter function is largely pulled from sglist_append_bio(), and sglist_append_bio() now uses sglist_append_vmpages(). Reviewed by: kib Sponsored by: Chelsio Communications
2016-05-20 23:28:43 +00:00
sglist.9 sglist_append_vmpages.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 sglist_build.9 \
sglist.9 sglist_clone.9 \
sglist.9 sglist_consume_uio.9 \
sglist.9 sglist_count.9 \
Fixup for r360574: install new mlinks for sglist(9) and remove old ones.
2020-07-07 02:41:51 +00:00
sglist.9 sglist_count_mbuf_epg.9 \
Add sglist functions for working with arrays of VM pages. sglist_count_vmpages() determines the number of segments required for a buffer described by an array of VM pages. sglist_append_vmpages() adds the segments described by such a buffer to an sglist. The latter function is largely pulled from sglist_append_bio(), and sglist_append_bio() now uses sglist_append_vmpages(). Reviewed by: kib Sponsored by: Chelsio Communications
2016-05-20 23:28:43 +00:00
sglist.9 sglist_count_vmpages.9 \
Add a simple API to manage scatter/gather lists of phyiscal addresses. Each list describes a logical memory object that is backed by one or more physical address ranges. To minimize locking, the sglist objects themselves are immutable once they are shared. These objects may be used in the future to facilitate I/O requests using physically-addressed buffers. For the immediate future I plan to use them to implement a new type of VM object and pager. Reviewed by: jeff, scottl MFC after: 1 month
2009-06-01 20:35:39 +00:00
sglist.9 sglist_free.9 \
sglist.9 sglist_hold.9 \
sglist.9 sglist_init.9 \
sglist.9 sglist_join.9 \
sglist.9 sglist_length.9 \
sglist.9 sglist_reset.9 \
sglist.9 sglist_slice.9 \
sglist.9 sglist_split.9
Add a helper API to allow in-kernel code to map portions of shared memory objects created by shm_open(2) into the kernel's address space. This provides a convenient way for creating shared memory buffers between userland and the kernel without requiring custom character devices.
2011-12-14 22:22:19 +00:00
MLINKS+=shm_map.9 shm_unmap.9
Bring signal(9) in sync with -current. Reviewed by: ru (mdoc changes)
2004-11-20 02:11:42 +00:00
MLINKS+=signal.9 cursig.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
signal.9 execsigs.9 \
signal.9 issignal.9 \
signal.9 killproc.9 \
signal.9 pgsigio.9 \
signal.9 postsig.9 \
signal.9 SETSETNEQ.9 \
signal.9 SETSETOR.9 \
signal.9 SIGADDSET.9 \
signal.9 SIG_CONTSIGMASK.9 \
signal.9 SIGDELSET.9 \
signal.9 SIGEMPTYSET.9 \
signal.9 sigexit.9 \
signal.9 SIGFILLSET.9 \
signal.9 siginit.9 \
signal.9 SIGISEMPTY.9 \
signal.9 SIGISMEMBER.9 \
signal.9 SIGNOTEMPTY.9 \
signal.9 signotify.9 \
signal.9 SIGPENDING.9 \
signal.9 SIGSETAND.9 \
signal.9 SIGSETCANTMASK.9 \
signal.9 SIGSETEQ.9 \
signal.9 SIGSETNAND.9 \
signal.9 SIG_STOPSIGMASK.9 \
signal.9 trapsignal.9
MLINKS+=sleep.9 msleep.9 \
MFcalloutng: Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9) KPIs. Also document recent changes in timeout(9) and eventtimers(4).
2013-03-04 19:10:39 +00:00
sleep.9 msleep_sbt.9 \
- Don't list sleep() in the NAME section as we haven't had a sleep() function in years. - Change the 'ident' paramters to 'wchan' to match <sys/systm.h>. - Use 'otherwise' in place of 'else' in one place so that this reads like English rather than C. - Document the new msleep_spin() function. - Add history notes for msleep() and msleep_spin().
2006-01-03 17:00:38 +00:00
sleep.9 msleep_spin.9 \
MFcalloutng: Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9) KPIs. Also document recent changes in timeout(9) and eventtimers(4).
2013-03-04 19:10:39 +00:00
sleep.9 msleep_spin_sbt.9 \
Add a new kernel sleep function pause(9). pause(9) is for places that want an equivalent of DELAY(9) that sleeps instead of spins. It accepts a wmesg and a timeout and is not interrupted by signals. It uses a private wait channel that should never be woken up by wakeup(9) or wakeup_one(9). Glanced at by: phk
2007-02-23 16:22:09 +00:00
sleep.9 pause.9 \
Document pause_sig(9) and update prototypes for existing pause(9) and pause_sbt(9) functions. MFC after: 1 week Suggested by: cem@ Sponsored by: Mellanox Technologies
2018-03-03 23:08:49 +00:00
sleep.9 pause_sig.9 \
MFcalloutng: Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9) KPIs. Also document recent changes in timeout(9) and eventtimers(4).
2013-03-04 19:10:39 +00:00
sleep.9 pause_sbt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sleep.9 tsleep.9 \
MFcalloutng: Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9) KPIs. Also document recent changes in timeout(9) and eventtimers(4).
2013-03-04 19:10:39 +00:00
sleep.9 tsleep_sbt.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sleep.9 wakeup.9 \
Add wakeup_any(), cheaper wakeup_one() for taskqueue(9). wakeup_one() and underlying sleepq_signal() spend additional time trying to be fair, waking thread with highest priority, sleeping longest time. But in case of taskqueue there are many absolutely identical threads, and any fairness between them is quite pointless. It makes even worse, since round-robin wakeups not only make previous CPU affinity in scheduler quite useless, but also hide from user chance to see CPU bottlenecks, when sequential workload with one request at a time looks evenly distributed between multiple threads. This change adds new SLEEPQ_UNFAIR flag to sleepq_signal(), making it wakeup thread that went to sleep last, but no longer in context switch (to avoid immediate spinning on the thread lock). On top of that new wakeup_any() function is added, equivalent to wakeup_one(), but setting the flag. On top of that taskqueue(9) is switchied to wakeup_any() to wakeup its threads. As result, on 72-core Xeon v4 machine sequential ZFS write to 12 ZVOLs with 16KB block size spend 34% less time in wakeup_any() and descendants then it was spending in wakeup_one(), and total write throughput increased by ~10% with the same as before CPU usage. Reviewed by: markj, mmacy MFC after: 2 weeks Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D20669
2019-06-20 01:15:33 +00:00
sleep.9 wakeup_one.9 \
sleep.9 wakeup_any.9
Rewrite sleepqueue manpage to catch up to the new sleep queue interface.
2004-03-12 19:07:18 +00:00
MLINKS+=sleepqueue.9 init_sleepqueues.9 \
sleepqueue.9 sleepq_abort.9 \
sleepqueue.9 sleepq_add.9 \
sleepqueue.9 sleepq_alloc.9 \
sleepqueue.9 sleepq_broadcast.9 \
sleepqueue.9 sleepq_free.9 \
sleepqueue.9 sleepq_lookup.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
sleepqueue.9 sleepq_lock.9 \
Rewrite sleepqueue manpage to catch up to the new sleep queue interface.
2004-03-12 19:07:18 +00:00
sleepqueue.9 sleepq_release.9 \
sleepqueue.9 sleepq_remove.9 \
sleepqueue.9 sleepq_set_timeout.9 \
MFcalloutng: Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9) KPIs. Also document recent changes in timeout(9) and eventtimers(4).
2013-03-04 19:10:39 +00:00
sleepqueue.9 sleepq_set_timeout_sbt.9 \
Sort MAN and MLINKS in dictionary order ignoring case.
2004-09-19 05:17:21 +00:00
sleepqueue.9 sleepq_signal.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
sleepqueue.9 sleepq_sleepcnt.9 \
Rewrite sleepqueue manpage to catch up to the new sleep queue interface.
2004-03-12 19:07:18 +00:00
sleepqueue.9 sleepq_timedwait.9 \
sleepqueue.9 sleepq_timedwait_sig.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
sleepqueue.9 sleepq_type.9 \
Rewrite sleepqueue manpage to catch up to the new sleep queue interface.
2004-03-12 19:07:18 +00:00
sleepqueue.9 sleepq_wait.9 \
sleepqueue.9 sleepq_wait_sig.9
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
MLINKS+=socket.9 soabort.9 \
socket.9 soaccept.9 \
socket.9 sobind.9 \
socket.9 socheckuid.9 \
Add a basic man page for the socket(9) kernel programming interface used by the NFS client and server, netsmb, netncp, etc. Reviewed by: ru Fixed by: ru
2006-12-15 23:35:15 +00:00
socket.9 soclose.9 \
socket.9 soconnect.9 \
socket.9 socreate.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 sodisconnect.9 \
Create a symlink for sodtor_set(9) to the socket(9) man page.
2018-06-08 19:47:04 +00:00
socket.9 sodtor_set.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 sodupsockaddr.9 \
socket.9 sofree.9 \
Add a basic man page for the socket(9) kernel programming interface used by the NFS client and server, netsmb, netncp, etc. Reviewed by: ru Fixed by: ru
2006-12-15 23:35:15 +00:00
socket.9 sogetopt.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 sohasoutofband.9 \
socket.9 solisten.9 \
socket.9 solisten_proto.9 \
socket.9 solisten_proto_check.9 \
socket.9 sonewconn.9 \
socket.9 sooptcopyin.9 \
socket.9 sooptcopyout.9 \
socket.9 sopoll.9 \
socket.9 sopoll_generic.9 \
Add a basic man page for the socket(9) kernel programming interface used by the NFS client and server, netsmb, netncp, etc. Reviewed by: ru Fixed by: ru
2006-12-15 23:35:15 +00:00
socket.9 soreceive.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 soreceive_dgram.9 \
socket.9 soreceive_generic.9 \
socket.9 soreceive_stream.9 \
socket.9 soreserve.9 \
socket.9 sorflush.9 \
Add a basic man page for the socket(9) kernel programming interface used by the NFS client and server, netsmb, netncp, etc. Reviewed by: ru Fixed by: ru
2006-12-15 23:35:15 +00:00
socket.9 sosend.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 sosend_dgram.9 \
socket.9 sosend_generic.9 \
Sort MLINKS.
2007-10-26 11:01:17 +00:00
socket.9 sosetopt.9 \
Document some more socket features Add some mention of the functions used by protocol implementations, upcalls, and other general routines. Not all functionality is documented; in particular: o the *at() variants, which are useful only for implementing the corresponding syscalls. o soconnect2(), also only used to implement a syscall (socketpair()). o sockargs(), which is essentually unused and only tangentially socket-related. o selsocket(), which is commented as being present solely for use by netncp and netsmb. o getsockaddr(), which is just a convenience shortcut for copyin(). Reviewed by: jhb (previous version) Approved by: hrs (mentor)
2014-06-02 03:03:57 +00:00
socket.9 soshutdown.9 \
socket.9 sotoxsocket.9 \
socket.9 soupcall_clear.9 \
socket.9 soupcall_set.9 \
socket.9 sowakeup.9
Add a man page for stack(9). MFC after: 1 week
2007-11-27 11:02:41 +00:00
MLINKS+=stack.9 stack_copy.9 \
stack.9 stack_create.9 \
stack.9 stack_destroy.9 \
Add stack_print_ddb() to the synposis of stack(9), add mlink for it; fix stack_print(9) mlink. Spotted by: attilio
2008-03-14 13:13:37 +00:00
stack.9 stack_print.9 \
stack.9 stack_print_ddb.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
stack.9 stack_print_short.9 \
stack.9 stack_print_short_ddb.9 \
Add a man page for stack(9). MFC after: 1 week
2007-11-27 11:02:41 +00:00
stack.9 stack_put.9 \
stack.9 stack_save.9 \
stack.9 stack_sbuf_print.9 \
Modify stack(9) stack_print() and stack_sbuf_print() routines to use new linker interfaces for looking up function names and offsets from instruction pointers. Create two variants of each call: one that is "DDB-safe" and avoids locking in the linker, and one that is safe for use in live kernels, by virtue of observing locking, and in particular safe when kernel modules are being loaded and unloaded simultaneous to their use. This will allow them to be used outside of debugging contexts. Modify two of three current stack(9) consumers to use the DDB-safe interfaces, as they run in low-level debugging contexts, such as inside lockmgr(9) and the kernel memory allocator. Update man page.
2007-12-01 22:04:16 +00:00
stack.9 stack_sbuf_print_ddb.9 \
Add a man page for stack(9). MFC after: 1 week
2007-11-27 11:02:41 +00:00
stack.9 stack_zero.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=store.9 subyte.9 \
Make fetch(9) and store(9) manual pages closer to reality.
2009-10-05 15:16:28 +00:00
store.9 suword.9 \
store.9 suword16.9 \
store.9 suword32.9 \
store.9 suword64.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=swi.9 swi_add.9 \
Document swi_remove(9). Reviewed by: jhb MFC after: 1 week
2012-04-19 15:29:09 +00:00
swi.9 swi_remove.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
swi.9 swi_sched.9
MLINKS+=sx.9 sx_assert.9 \
sx.9 sx_destroy.9 \
sx.9 sx_downgrade.9 \
sx.9 sx_init.9 \
Optimize sx locks to use simple atomic operations for the common cases of obtaining and releasing shared and exclusive locks. The algorithms for manipulating the lock cookie are very similar to that rwlocks. This patch also adds support for exclusive locks using the same algorithm as mutexes. A new sx_init_flags() function has been added so that optional flags can be specified to alter a given locks behavior. The flags include SX_DUPOK, SX_NOWITNESS, SX_NOPROFILE, and SX_QUITE which are all identical in nature to the similar flags for mutexes. Adaptive spinning on select locks may be enabled by enabling the ADAPTIVE_SX kernel option. Only locks initialized with the SX_ADAPTIVESPIN flag via sx_init_flags() will adaptively spin. The common cases for sx_slock(), sx_sunlock(), sx_xlock(), and sx_xunlock() are now performed inline in non-debug kernels. As a result, <sys/sx.h> now requires <sys/lock.h> to be included prior to <sys/sx.h>. The new kernel option SX_NOINLINE can be used to disable the aforementioned inlining in non-debug kernels. The size of struct sx has changed, so the kernel ABI is probably greatly disturbed. MFC after: 1 month Submitted by: attilio Tested by: kris, pjd
2007-03-31 23:23:42 +00:00
sx.9 sx_init_flags.9 \
Sort MLINKS.
2007-10-26 11:01:17 +00:00
sx.9 sx_sleep.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sx.9 sx_slock.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
sx.9 sx_slock_sig.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sx.9 sx_sunlock.9 \
sx.9 SX_SYSINIT.9 \
Clean up the SYSINIT_FLAGS definitions for rwlock(9) and rmlock(9). Avoid duplication in their macro definitions, and document them. No functional change intended. MFC after: 1 week
2017-11-21 14:59:23 +00:00
sx.9 SX_SYSINIT_FLAGS.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sx.9 sx_try_slock.9 \
sx.9 sx_try_upgrade.9 \
sx.9 sx_try_xlock.9 \
- Sort functions in the order that rwlock(9) and mutex(9) use. - Markup sx_unlock() as a function rather than saying it is a macro. The macro part is an implementation detail, and all the other sx_*lock() functions are actually macros, too. - Use the same style as rwlock(9) and mutex(9) to markup sx_assert() and SX_SYSINIT() with respect to headers and kernel options. - Add a missing MLINK.
2007-03-09 16:52:26 +00:00
sx.9 sx_unlock.9 \
Document sx_xholder().
2007-05-19 20:24:32 +00:00
sx.9 sx_xholder.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
sx.9 sx_xlock.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
sx.9 sx_xlock_sig.9 \
o Sort sx(9) MLINKS.
2006-07-12 19:12:16 +00:00
sx.9 sx_xlocked.9 \
sx.9 sx_xunlock.9
Document syscall_helper_register(9), syscall_helper_unregister(9)
2018-02-10 20:34:09 +00:00
MLINKS+=syscall_helper_register.9 syscall_helper_unregister.9 \
syscall_helper_register.9 SYSCALL_INIT_HELPER.9 \
syscall_helper_register.9 SYSCALL_INIT_HELPER_COMPAT.9 \
syscall_helper_register.9 SYSCALL_INIT_HELPER_COMPAT_F.9 \
syscall_helper_register.9 SYSCALL_INIT_HELPER_F.9
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
MLINKS+=sysctl.9 SYSCTL_DECL.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ADD_INT.9 \
sysctl.9 SYSCTL_ADD_LONG.9 \
sysctl.9 SYSCTL_ADD_NODE.9 \
Add support for attaching aggregation labels to sysctl objects. I'm currently working on writing a metrics exporter for the Prometheus monitoring system to provide access to sysctl metrics. Prometheus and sysctl have some structural differences: - sysctl is a tree of string component names. - Prometheus uses a flat namespace for its metrics, but allows you to attach labels with values to them, so that you can do aggregation. An initial version of my exporter simply translated hw.acpi.thermal.tz1.temperature to sysctl_hw_acpi_thermal_tz1_temperature_celcius while we should ideally have sysctl_hw_acpi_thermal_temperature_celcius{thermal_zone="tz1"} allowing you to graph all thermal zones on a system in one go. The change presented in this commit adds support for accomplishing this, by providing the ability to attach labels to nodes. In the example I gave above, the label "thermal_zone" would be attached to "tz1". As this is a feature that will only be used very rarely, I decided to not change the KPI too aggressively. Discussed on: hackers@ Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D8775
2016-12-14 12:47:34 +00:00
sysctl.9 SYSCTL_ADD_NODE_WITH_LABEL.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ADD_OPAQUE.9 \
sysctl.9 SYSCTL_ADD_PROC.9 \
sysctl.9 SYSCTL_ADD_QUAD.9 \
sysctl.9 SYSCTL_ADD_ROOT_NODE.9 \
Round out SYSCTL macros to the full set of fixed-width types Add S8, S16, S32, and U32 types; add SYSCTL*() macros for them, as well as for the existing 64-bit types. (While SYSCTL*QUAD and UQUAD macros already exist, they do not take the same sort of 'val' parameter that the other macros do.) Clean up the documented "types" in the sysctl.9 document. (These are macros and thus not real types, but the manual page documents intent.) The sysctl_add_oid(9) arg2 has been bumped from intptr_t to intmax_t to accommodate 64-bit types on 32-bit pointer architectures. This is just the kernel support piece; the userspace sysctl(1) support will follow in a later patch. Submitted by: Ravi Pokala <rpokala@panasas.com> Reviewed by: cem Relnotes: no Sponsored by: Panasas Differential Revision: https://reviews.freebsd.org/D4091
2015-11-07 01:43:01 +00:00
sysctl.9 SYSCTL_ADD_S8.9 \
sysctl.9 SYSCTL_ADD_S16.9 \
sysctl.9 SYSCTL_ADD_S32.9 \
sysctl.9 SYSCTL_ADD_S64.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ADD_STRING.9 \
sysctl.9 SYSCTL_ADD_STRUCT.9 \
Make the warning intervals for deprecated crypto algorithms tunable. New sysctl/tunables can now set the interval (in seconds) between rate-limited crypto warnings. The new sysctls are: - kern.cryptodev_warn_interval for /dev/crypto - net.inet.ipsec.crypto_warn_interval for IPsec - kern.kgssapi_warn_interval for KGSSAPI Reviewed by: cem MFC after: 1 month Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D20555
2019-06-11 23:00:55 +00:00
sysctl.9 SYSCTL_ADD_TIMEVAL_SEC.9 \
sysctl(9): Document U8/U16 types from r289773 Suggested by: ngie Sponsored by: EMC / Isilon Storage Division
2015-10-23 15:08:16 +00:00
sysctl.9 SYSCTL_ADD_U8.9 \
sysctl.9 SYSCTL_ADD_U16.9 \
Round out SYSCTL macros to the full set of fixed-width types Add S8, S16, S32, and U32 types; add SYSCTL*() macros for them, as well as for the existing 64-bit types. (While SYSCTL*QUAD and UQUAD macros already exist, they do not take the same sort of 'val' parameter that the other macros do.) Clean up the documented "types" in the sysctl.9 document. (These are macros and thus not real types, but the manual page documents intent.) The sysctl_add_oid(9) arg2 has been bumped from intptr_t to intmax_t to accommodate 64-bit types on 32-bit pointer architectures. This is just the kernel support piece; the userspace sysctl(1) support will follow in a later patch. Submitted by: Ravi Pokala <rpokala@panasas.com> Reviewed by: cem Relnotes: no Sponsored by: Panasas Differential Revision: https://reviews.freebsd.org/D4091
2015-11-07 01:43:01 +00:00
sysctl.9 SYSCTL_ADD_U32.9 \
sysctl.9 SYSCTL_ADD_U64.9 \
Fix multiple incorrect SYSCTL arguments in the kernel: - Wrong integer type was specified. - Wrong or missing "access" specifier. The "access" specifier sometimes included the SYSCTL type, which it should not, except for procedural SYSCTL nodes. - Logical OR where binary OR was expected. - Properly assert the "access" argument passed to all SYSCTL macros, using the CTASSERT macro. This applies to both static- and dynamically created SYSCTLs. - Properly assert the the data type for both static and dynamic SYSCTLs. In the case of static SYSCTLs we only assert that the data pointed to by the SYSCTL data pointer has the correct size, hence there is no easy way to assert types in the C language outside a C-function. - Rewrote some code which doesn't pass a constant "access" specifier when creating dynamic SYSCTL nodes, which is now a requirement. - Updated "EXAMPLES" section in SYSCTL manual page. MFC after: 3 days Sponsored by: Mellanox Technologies
2014-10-21 07:31:21 +00:00
sysctl.9 SYSCTL_ADD_UAUTO.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ADD_UINT.9 \
sysctl.9 SYSCTL_ADD_ULONG.9 \
Sort UMA macros and create MLINKS for them This patch is a follow-up to r344518. Reported by: ngie Reviewed by: hselasky Differential Revision: https://reviews.freebsd.org/D24165
2020-03-23 14:04:42 +00:00
sysctl.9 SYSCTL_ADD_UMA_CUR.9 \
sysctl.9 SYSCTL_ADD_UMA_MAX.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ADD_UQUAD.9 \
sysctl.9 SYSCTL_CHILDREN.9 \
sysctl.9 SYSCTL_STATIC_CHILDREN.9 \
sysctl.9 SYSCTL_NODE_CHILDREN.9 \
sysctl.9 SYSCTL_PARENT.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_INT.9 \
Add support for attaching aggregation labels to sysctl objects. I'm currently working on writing a metrics exporter for the Prometheus monitoring system to provide access to sysctl metrics. Prometheus and sysctl have some structural differences: - sysctl is a tree of string component names. - Prometheus uses a flat namespace for its metrics, but allows you to attach labels with values to them, so that you can do aggregation. An initial version of my exporter simply translated hw.acpi.thermal.tz1.temperature to sysctl_hw_acpi_thermal_tz1_temperature_celcius while we should ideally have sysctl_hw_acpi_thermal_temperature_celcius{thermal_zone="tz1"} allowing you to graph all thermal zones on a system in one go. The change presented in this commit adds support for accomplishing this, by providing the ability to attach labels to nodes. In the example I gave above, the label "thermal_zone" would be attached to "tz1". As this is a feature that will only be used very rarely, I decided to not change the KPI too aggressively. Discussed on: hackers@ Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D8775
2016-12-14 12:47:34 +00:00
sysctl.9 SYSCTL_INT_WITH_LABEL.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_LONG.9 \
Document sysctl nodes that translate their values. This documents the behavior of sysctl_msec_to_ticks and SYSCTL_{ADD,}_SBINTIME_[UM]SEC. Reviewed by: cem MFC after: 1 week Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D20596
2019-06-11 22:57:25 +00:00
sysctl.9 sysctl_msec_to_ticks.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_NODE.9 \
Add support for attaching aggregation labels to sysctl objects. I'm currently working on writing a metrics exporter for the Prometheus monitoring system to provide access to sysctl metrics. Prometheus and sysctl have some structural differences: - sysctl is a tree of string component names. - Prometheus uses a flat namespace for its metrics, but allows you to attach labels with values to them, so that you can do aggregation. An initial version of my exporter simply translated hw.acpi.thermal.tz1.temperature to sysctl_hw_acpi_thermal_tz1_temperature_celcius while we should ideally have sysctl_hw_acpi_thermal_temperature_celcius{thermal_zone="tz1"} allowing you to graph all thermal zones on a system in one go. The change presented in this commit adds support for accomplishing this, by providing the ability to attach labels to nodes. In the example I gave above, the label "thermal_zone" would be attached to "tz1". As this is a feature that will only be used very rarely, I decided to not change the KPI too aggressively. Discussed on: hackers@ Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D8775
2016-12-14 12:47:34 +00:00
sysctl.9 SYSCTL_NODE_WITH_LABEL.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_OPAQUE.9 \
sysctl.9 SYSCTL_PROC.9 \
- Document the UQUAD sysctl variants. - Clarify that exactly one of the "access" flags is required and list the optional flags in a separate list. Prefer bundling CTLFLAG_TUN into the access flag by not documenting it as an optional flag to set. Approved by: re (glebius) MFC after: 1 week
2013-09-12 20:49:20 +00:00
sysctl.9 SYSCTL_QUAD.9 \
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
sysctl.9 SYSCTL_ROOT_NODE.9 \
Round out SYSCTL macros to the full set of fixed-width types Add S8, S16, S32, and U32 types; add SYSCTL*() macros for them, as well as for the existing 64-bit types. (While SYSCTL*QUAD and UQUAD macros already exist, they do not take the same sort of 'val' parameter that the other macros do.) Clean up the documented "types" in the sysctl.9 document. (These are macros and thus not real types, but the manual page documents intent.) The sysctl_add_oid(9) arg2 has been bumped from intptr_t to intmax_t to accommodate 64-bit types on 32-bit pointer architectures. This is just the kernel support piece; the userspace sysctl(1) support will follow in a later patch. Submitted by: Ravi Pokala <rpokala@panasas.com> Reviewed by: cem Relnotes: no Sponsored by: Panasas Differential Revision: https://reviews.freebsd.org/D4091
2015-11-07 01:43:01 +00:00
sysctl.9 SYSCTL_S8.9 \
sysctl.9 SYSCTL_S16.9 \
sysctl.9 SYSCTL_S32.9 \
sysctl.9 SYSCTL_S64.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_STRING.9 \
sysctl.9 SYSCTL_STRUCT.9 \
Make the warning intervals for deprecated crypto algorithms tunable. New sysctl/tunables can now set the interval (in seconds) between rate-limited crypto warnings. The new sysctls are: - kern.cryptodev_warn_interval for /dev/crypto - net.inet.ipsec.crypto_warn_interval for IPsec - kern.kgssapi_warn_interval for KGSSAPI Reviewed by: cem MFC after: 1 month Relnotes: yes Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D20555
2019-06-11 23:00:55 +00:00
sysctl.9 SYSCTL_TIMEVAL_SEC.9 \
sysctl(9): Document U8/U16 types from r289773 Suggested by: ngie Sponsored by: EMC / Isilon Storage Division
2015-10-23 15:08:16 +00:00
sysctl.9 SYSCTL_U8.9 \
sysctl.9 SYSCTL_U16.9 \
Round out SYSCTL macros to the full set of fixed-width types Add S8, S16, S32, and U32 types; add SYSCTL*() macros for them, as well as for the existing 64-bit types. (While SYSCTL*QUAD and UQUAD macros already exist, they do not take the same sort of 'val' parameter that the other macros do.) Clean up the documented "types" in the sysctl.9 document. (These are macros and thus not real types, but the manual page documents intent.) The sysctl_add_oid(9) arg2 has been bumped from intptr_t to intmax_t to accommodate 64-bit types on 32-bit pointer architectures. This is just the kernel support piece; the userspace sysctl(1) support will follow in a later patch. Submitted by: Ravi Pokala <rpokala@panasas.com> Reviewed by: cem Relnotes: no Sponsored by: Panasas Differential Revision: https://reviews.freebsd.org/D4091
2015-11-07 01:43:01 +00:00
sysctl.9 SYSCTL_U32.9 \
sysctl.9 SYSCTL_U64.9 \
Add MLINKS entries for various SYSCTL_*() macros documented in sysctl.9. Approved by: re (bmah) Submitted by: Constantine A. Murenin <cnst+freebsd@bugmail.mojo.ru> Sponsored by: Google Summer of Code 2007
2007-09-05 19:46:23 +00:00
sysctl.9 SYSCTL_UINT.9 \
sysctl.9 SYSCTL_ULONG.9 \
Sort UMA macros and create MLINKS for them This patch is a follow-up to r344518. Reported by: ngie Reviewed by: hselasky Differential Revision: https://reviews.freebsd.org/D24165
2020-03-23 14:04:42 +00:00
sysctl.9 SYSCTL_UMA_CUR.9 \
sysctl.9 SYSCTL_UMA_MAX.9 \
- Document the UQUAD sysctl variants. - Clarify that exactly one of the "access" flags is required and list the optional flags in a separate list. Prefer bundling CTLFLAG_TUN into the access flag by not documenting it as an optional flag to set. Approved by: re (glebius) MFC after: 1 week
2013-09-12 20:49:20 +00:00
sysctl.9 SYSCTL_UQUAD.9
- Updated SYSCTL manual pages after recent changes to the kernel SYSCTL code. Added description of new macros and functions. - Merged dynamic and static SYSCTL related content into a single manual page, hence parameters and functionality is very much the same. - Uppercased all occurrences of "OID". - Updated all SYSCTL examples. PR: 192101
2014-07-31 17:18:40 +00:00
MLINKS+=sysctl_add_oid.9 sysctl_move_oid.9 \
Add description of "sysctl_remove_name()" function.
2014-08-28 04:35:38 +00:00
sysctl_add_oid.9 sysctl_remove_oid.9 \
sysctl_add_oid.9 sysctl_remove_name.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=sysctl_ctx_init.9 sysctl_ctx_entry_add.9 \
sysctl_ctx_init.9 sysctl_ctx_entry_del.9 \
sysctl_ctx_init.9 sysctl_ctx_entry_find.9 \
sysctl_ctx_init.9 sysctl_ctx_free.9
Add a manpage for SYSINIT() and SYSUNINIT(). PR: docs/132884 Submitted by: pluknet, hmp
2010-12-06 15:19:03 +00:00
MLINKS+=SYSINIT.9 SYSUNINIT.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=taskqueue.9 TASK_INIT.9 \
Add a TASK_INITIALIZER() macro that can be used to statically initialize a task structure. Reviewed by: gj MFC after: 2 weeks
2011-12-19 18:55:13 +00:00
taskqueue.9 TASK_INITIALIZER.9 \
update taskqueue(9) manual page Many thanks to bjk, gjb and pluknet for improvements and suggestions. MFC after: 5 days Sponsored by: HybridCluster
2014-02-14 15:03:55 +00:00
taskqueue.9 taskqueue_block.9 \
Add a taskqueue_cancel(9) to cancel a pending task without waiting for it to run as taskqueue_drain(9) does. Requested by: hselasky Original code: jeff Reviewed by: jhb MFC after: 2 weeks
2010-11-08 20:56:31 +00:00
taskqueue.9 taskqueue_cancel.9 \
Add missing links to taskqueue(9). MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-18 13:39:47 +00:00
taskqueue.9 taskqueue_cancel_timeout.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
taskqueue.9 taskqueue_create.9 \
Update links for taskqueue(9) functions.
2010-10-18 12:35:48 +00:00
taskqueue.9 taskqueue_create_fast.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
taskqueue.9 TASKQUEUE_DECLARE.9 \
taskqueue.9 TASKQUEUE_DEFINE.9 \
Update links for taskqueue(9) functions.
2010-10-18 12:35:48 +00:00
taskqueue.9 TASKQUEUE_DEFINE_THREAD.9 \
taskqueue.9 taskqueue_drain.9 \
update taskqueue(9) manual page Many thanks to bjk, gjb and pluknet for improvements and suggestions. MFC after: 5 days Sponsored by: HybridCluster
2014-02-14 15:03:55 +00:00
taskqueue.9 taskqueue_drain_all.9 \
Add missing links to taskqueue(9). MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-18 13:39:47 +00:00
taskqueue.9 taskqueue_drain_timeout.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
taskqueue.9 taskqueue_enqueue.9 \
Add missing links to taskqueue(9). MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-18 13:39:47 +00:00
taskqueue.9 taskqueue_enqueue_timeout.9 \
Update links for taskqueue(9) functions.
2010-10-18 12:35:48 +00:00
taskqueue.9 TASKQUEUE_FAST_DEFINE.9 \
taskqueue.9 TASKQUEUE_FAST_DEFINE_THREAD.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
taskqueue.9 taskqueue_free.9 \
Update links for taskqueue(9) functions.
2010-10-18 12:35:48 +00:00
taskqueue.9 taskqueue_member.9 \
Add a taskqueue_quiesce(9) KPI. This is similar to taskqueue_drain_all(9) but will wait for the queue to become idle before returning instead of only waiting for already-enqueued tasks to finish. This will be used in the opensolaris compat layer. PR: 227784 Reviewed by: cem MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D17975
2018-11-21 17:18:27 +00:00
taskqueue.9 taskqueue_quiesce.9 \
update taskqueue(9) manual page Many thanks to bjk, gjb and pluknet for improvements and suggestions. MFC after: 5 days Sponsored by: HybridCluster
2014-02-14 15:03:55 +00:00
taskqueue.9 taskqueue_run.9 \
Add missing links to taskqueue(9). MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-18 13:39:47 +00:00
taskqueue.9 taskqueue_set_callback.9 \
taskqueue.9 taskqueue_start_threads.9 \
document taskqueue_start_threads_in_proc While here, fix taskqueue_start_threads_cpuset that was documented under old name of taskqueue_start_threads_pinned. MFC after: 4 weeks
2019-10-17 06:58:07 +00:00
taskqueue.9 taskqueue_start_threads_cpuset.9 \
taskqueue.9 taskqueue_start_threads_in_proc.9 \
Add missing link to TIMEOUT_TASK_INIT(9). MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-18 13:56:32 +00:00
taskqueue.9 taskqueue_unblock.9 \
taskqueue.9 TIMEOUT_TASK_INIT.9
Document support for alternate TCP stacks. Differential Revision: https://reviews.freebsd.org/D6940 Reviewed by: hiren Approved by: re (gjb) Sponsored by: Juniper Networks
2016-06-28 13:37:01 +00:00
MLINKS+=tcp_functions.9 register_tcp_functions.9 \
Add the infrastructure to support loading multiple versions of TCP stack modules. It adds support for mangling symbols exported by a module by prepending a string to them. (This avoids overlapping symbols in the kernel linker.) It allows the use of a macro as the module name in the DECLARE_MACRO() and MACRO_VERSION() macros. It allows the code to register stack aliases (e.g. both a generic name ["default"] and version-specific name ["default_10_3p1"]). With these changes, it is trivial to compile TCP stack modules with the name defined in the Makefile and to load multiple versions of the same stack simultaneously. This functionality can be used to enable side-by-side testing of an old and new version of the same TCP stack. It also could support upgrading the TCP stack without a reboot. Reviewed by: gnn, sjg (makefiles only) Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D11086
2017-06-08 20:41:28 +00:00
tcp_functions.9 register_tcp_functions_as_name.9 \
tcp_functions.9 register_tcp_functions_as_names.9 \
Document support for alternate TCP stacks. Differential Revision: https://reviews.freebsd.org/D6940 Reviewed by: hiren Approved by: re (gjb) Sponsored by: Juniper Networks
2016-06-28 13:37:01 +00:00
tcp_functions.9 deregister_tcp_functions.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=time.9 boottime.9 \
Bring kernel time variable and access function docs up to date by updating the list of variables and mentioning the bin(up)time functions.
2004-09-17 07:24:18 +00:00
time.9 time_second.9 \
time.9 time_uptime.9
Remove documentation for the nonexistant cred_update_thread(9). This was a tangential change submitted as part of D18930. Submitted by: jack@gandi.net
2019-01-23 23:25:42 +00:00
MLINKS+=ucred.9 crcopy.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ucred.9 crcopysafe.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
ucred.9 crdup.9 \
ucred.9 crfree.9 \
ucred.9 crget.9 \
ucred.9 crhold.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
ucred.9 crsetgroups.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
ucred.9 cru2x.9
MLINKS+=uidinfo.9 uifind.9 \
uidinfo.9 uifree.9 \
uidinfo.9 uihashinit.9 \
uidinfo.9 uihold.9
Document copyin_nofault, copyout_nofault, uiomove_nofault. Submitted by: alc
2011-07-09 15:24:12 +00:00
MLINKS+=uio.9 uiomove.9 \
Document uiomove_frombuf(9).
2017-03-11 22:22:51 +00:00
uio.9 uiomove_frombuf.9 \
Document copyin_nofault, copyout_nofault, uiomove_nofault. Submitted by: alc
2011-07-09 15:24:12 +00:00
uio.9 uiomove_nofault.9
Clean up more usb related files when MK_USB == no when dealing with manpages, libraries, and binaries
2014-11-26 21:18:52 +00:00
.if ${MK_USB} != "no"
MAN+= usbdi.9
Sort mlinks.
2009-12-22 16:02:08 +00:00
MLINKS+=usbdi.9 usbd_do_request.9 \
Add basic documentation for many of the kernel USB functions that USB device drivers use to talk to USB devices. This is probably still a bit rough and it does not yet include the functions specific to HID, ethernet, hubs, host controller drivers, task threads or debugging.
2005-12-31 03:53:02 +00:00
usbdi.9 usbd_do_request_flags.9 \
usbdi.9 usbd_errstr.9 \
Move programming info from usb(4) to usbdi(9) and update for the usb stack changeover. Needs much more content still.
2009-06-24 17:01:17 +00:00
usbdi.9 usbd_lookup_id_by_info.9 \
usbdi.9 usbd_lookup_id_by_uaa.9 \
usbdi.9 usbd_transfer_clear_stall.9 \
usbdi.9 usbd_transfer_drain.9 \
usbdi.9 usbd_transfer_pending.9 \
usbdi.9 usbd_transfer_poll.9 \
usbdi.9 usbd_transfer_setup.9 \
usbdi.9 usbd_transfer_start.9 \
usbdi.9 usbd_transfer_stop.9 \
usbdi.9 usbd_transfer_submit.9 \
usbdi.9 usbd_transfer_unsetup.9 \
usbdi.9 usbd_xfer_clr_flag.9 \
usbdi.9 usbd_xfer_frame_data.9 \
usbdi.9 usbd_xfer_frame_len.9 \
usbdi.9 usbd_xfer_get_frame.9 \
usbdi.9 usbd_xfer_get_priv.9 \
usbdi.9 usbd_xfer_is_stalled.9 \
usbdi.9 usbd_xfer_max_framelen.9 \
usbdi.9 usbd_xfer_max_frames.9 \
usbdi.9 usbd_xfer_max_len.9 \
usbdi.9 usbd_xfer_set_flag.9 \
usbdi.9 usbd_xfer_set_frame_data.9 \
usbdi.9 usbd_xfer_set_frame_len.9 \
usbdi.9 usbd_xfer_set_frame_offset.9 \
usbdi.9 usbd_xfer_set_frames.9 \
usbdi.9 usbd_xfer_set_interval.9 \
usbdi.9 usbd_xfer_set_priv.9 \
usbdi.9 usbd_xfer_set_stall.9 \
usbdi.9 usbd_xfer_set_timeout.9 \
usbdi.9 usbd_xfer_softc.9 \
usbdi.9 usbd_xfer_state.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
usbdi.9 usbd_xfer_status.9 \
usbdi.9 usb_fifo_alloc_buffer.9 \
usbdi.9 usb_fifo_attach.9 \
usbdi.9 usb_fifo_detach.9 \
usbdi.9 usb_fifo_free_buffer.9 \
usbdi.9 usb_fifo_get_data.9 \
usbdi.9 usb_fifo_get_data_buffer.9 \
usbdi.9 usb_fifo_get_data_error.9 \
usbdi.9 usb_fifo_get_data_linear.9 \
usbdi.9 usb_fifo_put_bytes_max.9 \
usbdi.9 usb_fifo_put_data.9 \
usbdi.9 usb_fifo_put_data_buffer.9 \
usbdi.9 usb_fifo_put_data_error.9 \
usbdi.9 usb_fifo_put_data_linear.9 \
usbdi.9 usb_fifo_reset.9 \
usbdi.9 usb_fifo_softc.9 \
usbdi.9 usb_fifo_wakeup.9
Clean up more usb related files when MK_USB == no when dealing with manpages, libraries, and binaries
2014-11-26 21:18:52 +00:00
.endif
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=vcount.9 count_dev.9
MLINKS+=vfsconf.9 vfs_modevent.9 \
vfsconf.9 vfs_register.9 \
vfsconf.9 vfs_unregister.9
Sort MLINKS.
2007-10-26 11:01:17 +00:00
MLINKS+=vfs_getopt.9 vfs_copyopt.9 \
vfs_getopt.9 vfs_filteropt.9 \
Add vfs_getopt.9 to the build, and add links for related functions.
2007-03-02 17:03:56 +00:00
vfs_getopt.9 vfs_flagopt.9 \
Sort MLINKS.
2007-10-26 11:01:17 +00:00
vfs_getopt.9 vfs_getopts.9 \
Extend the "vfsopt" mount options for more general use. Make struct vfsopt and the vfs_buildopts function public, and add some new fields to struct vfsopt (pos and seen), and new functions vfs_getopt_pos and vfs_opterror. Further extend the interface to allow reading options from the kernel in addition to sending them to the kernel, with vfs_setopt and related functions. While this allows the "name=value" option interface to be used for more than just FS mounts (planned use is for jails), it retains the current "vfsopt" name and <sys/mount.h> requirement. Approved by: bz (mentor)
2009-03-02 23:26:30 +00:00
vfs_getopt.9 vfs_scanopt.9 \
vfs_getopt.9 vfs_setopt.9 \
vfs_getopt.9 vfs_setopt_part.9 \
vfs_getopt.9 vfs_setopts.9
o Document vdropl(9) [1]. o Add an MLINK for vdropl(). Reviewed by: des [1] Obtained from: wording from vgone(9)
2007-04-01 09:48:59 +00:00
MLINKS+=vhold.9 vdrop.9 \
Sort mlinks.
2009-12-22 16:02:08 +00:00
vhold.9 vdropl.9 \
vhold.9 vholdl.9
add links for the various vmem functions...
2013-09-04 17:48:41 +00:00
MLINKS+=vmem.9 vmem_add.9 \
vmem.9 vmem_alloc.9 \
vmem.9 vmem_create.9 \
vmem.9 vmem_destroy.9 \
vmem.9 vmem_free.9 \
vmem.9 vmem_xalloc.9 \
vmem.9 vmem_xfree.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=vm_map_lock.9 vm_map_lock_downgrade.9 \
vm_map_lock.9 vm_map_lock_read.9 \
vm_map_lock.9 vm_map_lock_upgrade.9 \
vm_map_lock.9 vm_map_trylock.9 \
vm_map_lock.9 vm_map_trylock_read.9 \
vm_map_lock.9 vm_map_unlock.9 \
vm_map_lock.9 vm_map_unlock_read.9
Add manual pages for the vm_map(9) part of the VM. Reviewed by: juli Approved by: jake (mentor)
2003-09-30 00:51:31 +00:00
MLINKS+=vm_map_lookup.9 vm_map_lookup_done.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=vm_map_max.9 vm_map_min.9 \
vm_map_max.9 vm_map_pmap.9
Add manual pages for the vm_map(9) part of the VM. Reviewed by: juli Approved by: jake (mentor)
2003-09-30 00:51:31 +00:00
MLINKS+=vm_map_stack.9 vm_map_growstack.9
Change synchonization rules for vm_page reference counting. There are several mechanisms by which a vm_page reference is held, preventing the page from being freed back to the page allocator. In particular, holding the page's object lock is sufficient to prevent the page from being freed; holding the busy lock or a wiring is sufficent as well. These references are protected by the page lock, which must therefore be acquired for many per-page operations. This results in false sharing since the page locks are external to the vm_page structures themselves and each lock protects multiple structures. Transition to using an atomically updated per-page reference counter. The object's reference is counted using a flag bit in the counter. A second flag bit is used to atomically block new references via pmap_extract_and_hold() while removing managed mappings of a page. Thus, the reference count of a page is guaranteed not to increase if the page is unbusied, unmapped, and the object's write lock is held. As a consequence of this, the page lock no longer protects a page's identity; operations which move pages between objects are now synchronized solely by the objects' locks. The vm_page_wire() and vm_page_unwire() KPIs are changed. The former requires that either the object lock or the busy lock is held. The latter no longer has a return value and may free the page if it releases the last reference to that page. vm_page_unwire_noq() behaves the same as before; the caller is responsible for checking its return value and freeing or enqueuing the page as appropriate. vm_page_wire_mapped() is introduced for use in pmap_extract_and_hold(). It fails if the page is concurrently being unmapped, typically triggering a fallback to the fault handler. vm_page_wire() no longer requires the page lock and vm_page_unwire() now internally acquires the page lock when releasing the last wiring of a page (since the page lock still protects a page's queue state). In particular, synchronization details are no longer leaked into the caller. The change excises the page lock from several frequently executed code paths. In particular, vm_object_terminate() no longer bounces between page locks as it releases an object's pages, and direct I/O and sendfile(SF_NOCACHE) completions no longer require the page lock. In these latter cases we now get linear scalability in the common scenario where different threads are operating on different files. __FreeBSD_version is bumped. The DRM ports have been updated to accomodate the KPI changes. Reviewed by: jeff (earlier version) Tested by: gallatin (earlier version), pho Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D20486
2019-09-09 21:32:42 +00:00
MLINKS+=vm_map_wire.9 vm_map_wire_mapped.9 \
vm_page_wire.9 vm_page_unwire.9 \
vm_page_wire.9 vm_page_unwire_noq.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=vm_page_bits.9 vm_page_clear_dirty.9 \
vm_page_bits.9 vm_page_dirty.9 \
vm_page_bits.9 vm_page_is_valid.9 \
vm_page_bits.9 vm_page_set_invalid.9 \
vm_page_bits.9 vm_page_set_validclean.9 \
vm_page_bits.9 vm_page_test_dirty.9 \
vm_page_bits.9 vm_page_undirty.9 \
vm_page_bits.9 vm_page_zero_invalid.9
The soft and hard busy mechanism rely on the vm object lock to work. Unify the 2 concept into a real, minimal, sxlock where the shared acquisition represent the soft busy and the exclusive acquisition represent the hard busy. The old VPO_WANTED mechanism becames the hard-path for this new lock and it becomes per-page rather than per-object. The vm_object lock becames an interlock for this functionality: it can be held in both read or write mode. However, if the vm_object lock is held in read mode while acquiring or releasing the busy state, the thread owner cannot make any assumption on the busy state unless it is also busying it. Also: - Add a new flag to directly shared busy pages while vm_page_alloc and vm_page_grab are being executed. This will be very helpful once these functions happen under a read object lock. - Move the swapping sleep into its own per-object flag The KPI is heavilly changed this is why the version is bumped. It is very likely that some VM ports users will need to change their own code. Sponsored by: EMC / Isilon storage division Discussed with: alc Reviewed by: jeff, kib Tested by: gavin, bapt (older version) Tested by: pho, scottl
2013-08-09 11:11:11 +00:00
MLINKS+=vm_page_busy.9 vm_page_busied.9 \
vm_page_busy.9 vm_page_busy_downgrade.9 \
vm_page_busy.9 vm_page_busy_sleep.9 \
vm_page_busy.9 vm_page_sbusied.9 \
vm_page_busy.9 vm_page_sbusy.9 \
vm_page_busy.9 vm_page_sleep_if_busy.9 \
vm_page_busy.9 vm_page_sunbusy.9 \
vm_page_busy.9 vm_page_trysbusy.9 \
vm_page_busy.9 vm_page_tryxbusy.9 \
vm_page_busy.9 vm_page_xbusied.9 \
vm_page_busy.9 vm_page_xbusy.9 \
vm_page_busy.9 vm_page_xunbusy.9 \
vm_page_busy.9 vm_page_assert_sbusied.9 \
vm_page_busy.9 vm_page_assert_unbusied.9 \
vm_page_busy.9 vm_page_assert_xbusied.9
Document vm_page_aflag_set(9), vm_page_aflag_clear(9) and vm_page_reference(9). Retire vm_page_flag_set() and vm_page_flag_clear() functions. Reviewed by: alc Approved by: re (bz)
2011-09-06 10:40:21 +00:00
MLINKS+=vm_page_aflag.9 vm_page_aflag_clear.9 \
vm_page_aflag.9 vm_page_aflag_set.9 \
vm_page_aflag.9 vm_page_reference.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=vm_page_free.9 vm_page_free_toq.9 \
vm_page_free.9 vm_page_free_zero.9 \
vm_page_free.9 vm_page_try_to_free.9
Install and provide MLINKS for: pbuf.9 vm_page_alloc.9 vm_page_copy.9 vm_page_flag.9 vm_page_hold.9 vm_page_insert.9 vm_page_io.9 vm_page_lookup.9 vm_page_protect.9 vm_page_sleep_busy.9 vm_page_wakeup.9 vm_page_wire.9 vm_page_zero_fill.9 vm_set_page_size.9
2001-07-18 06:10:33 +00:00
MLINKS+=vm_page_insert.9 vm_page_remove.9
MLINKS+=vm_page_wire.9 vm_page_unwire.9
Add VOP_ACCESSX, which can be used to query for newly added V* permissions, such as VWRITE_ACL. For a filsystems that don't implement it, there is a default implementation, which works as a wrapper around VOP_ACCESS. Reviewed by: rwatson@
2009-05-30 13:59:05 +00:00
MLINKS+=VOP_ACCESS.9 VOP_ACCESSX.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=VOP_ATTRIB.9 VOP_GETATTR.9 \
vfs: add VOP_STAT The current scheme of calling VOP_GETATTR adds avoidable overhead. An example with tmpfs doing fstat (ops/s): before: 7488958 after: 7913833 Reviewed by: kib (previous version) Differential Revision: https://reviews.freebsd.org/D25910
2020-08-07 23:06:40 +00:00
VOP_ATTRIB.9 VOP_SETATTR.9 \
VOP_ATTRIB.9 VOP_STAT.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=VOP_CREATE.9 VOP_MKDIR.9 \
VOP_CREATE.9 VOP_MKNOD.9 \
VOP_CREATE.9 VOP_SYMLINK.9
Add man page for VOP_FDATASYNC(9) Reviewed by: kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D19678
2019-03-22 18:42:34 +00:00
MLINKS+=VOP_FSYNC.9 VOP_FDATASYNC.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=VOP_GETPAGES.9 VOP_PUTPAGES.9
MLINKS+=VOP_INACTIVE.9 VOP_RECLAIM.9
MLINKS+=VOP_LOCK.9 vn_lock.9 \
VOP_LOCK.9 VOP_ISLOCKED.9 \
VOP_LOCK.9 VOP_UNLOCK.9
MLINKS+=VOP_OPENCLOSE.9 VOP_CLOSE.9 \
VOP_OPENCLOSE.9 VOP_OPEN.9
MLINKS+=VOP_RDWR.9 VOP_READ.9 \
VOP_RDWR.9 VOP_WRITE.9
MLINKS+=VOP_REMOVE.9 VOP_RMDIR.9
Create a vimage.9 link to vnet.9 Requested by: glebius
2014-11-21 17:57:37 +00:00
MLINKS+=vnet.9 vimage.9
Add link for vrefl(9). Sponsored by: Dell EMC Isilon MFC after: 1 week
2016-10-06 18:05:25 +00:00
MLINKS+=vref.9 VREF.9 \
vref.9 vrefl.9
Document vunref(9), add some important notes for vrele(9) and vput(9). Merge all three manpages to one, removing separate file for vput(9). MFC after: 1 week
2010-10-17 16:30:33 +00:00
MLINKS+=vrele.9 vput.9 \
vrele.9 vunref.9
Sorted lists. Use the same style as most Makefiles for `MLINKS+=' lines.
1998-01-01 10:12:14 +00:00
MLINKS+=vslock.9 vsunlock.9
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
MLINKS+=zone.9 uma.9 \
Extend uma_reclaim() to permit different reclamation targets. The page daemon periodically invokes uma_reclaim() to reclaim cached items from each zone when the system is under memory pressure. This is important since the size of these caches is unbounded by default. However it also results in bursts of high latency when allocating from heavily used zones as threads miss in the per-CPU caches and must access the keg in order to allocate new items. With r340405 we maintain an estimate of each zone's usage of its (per-NUMA domain) cache of full buckets. Start making use of this estimate to avoid reclaiming the entire cache when under memory pressure. In particular, introduce TRIM, DRAIN and DRAIN_CPU verbs for uma_reclaim() and uma_zone_reclaim(). When trimming, only items in excess of the estimate are reclaimed. Draining a zone reclaims all of the cached full buckets (the previous behaviour of uma_reclaim()), and may further drain the per-CPU caches in extreme cases. Now, when under memory pressure, the page daemon will trim zones rather than draining them. As a result, heavily used zones do not incur bursts of bucket cache misses following reclamation, but large, unused caches will be reclaimed as before. Reviewed by: jeff Tested by: pho (an earlier version) MFC after: 2 months Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D16667
2019-09-01 22:22:43 +00:00
zone.9 uma_prealloc.9 \
zone.9 uma_reclaim.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
zone.9 uma_zalloc.9 \
add a few missing links... Submitted by: J David MFC after: 1 week
2014-01-31 03:57:49 +00:00
zone.9 uma_zalloc_arg.9 \
Document new NUMA related syscalls and utility options. Sponsored by: Netflix, Dell/EMC Isilon
2018-03-24 23:58:44 +00:00
zone.9 uma_zalloc_domain.9 \
Update and clean up the UMA man page. - Fix warnings from igor and mandoc. - Provide a brief description of the separation between zones and their backend slab allocators. - Document cache zones and secondary zones. - Document the kernel config options added in r350659. - Document the uma_zalloc_pcpu() and uma_zfree_pcpu() wrappers. - Document uma_zone_reserve(), uma_zone_reserve_kva() and uma_zone_prealloc(). - Document uma_zone_alloc() and uma_zone_freef(). - Add some missing MLINKs and Xrefs. MFC after: 2 weeks
2019-08-30 19:35:44 +00:00
zone.9 uma_zalloc_pcpu.9 \
zone.9 uma_zalloc_pcpu_arg.9 \
zone.9 uma_zcache_create.9 \
Use a single style for share/man/ makefiles: - Sort MAN and MLINKS in "dictionary" order ignoring case. - For multi-value MAN and multi-pair MLINKS, put each value/pair on its own line, for easier sorting and so that further diffs are easier to see.
2004-01-20 10:27:23 +00:00
zone.9 uma_zcreate.9 \
zone.9 uma_zdestroy.9 \
zone.9 uma_zfree.9 \
add a few missing links... Submitted by: J David MFC after: 1 week
2014-01-31 03:57:49 +00:00
zone.9 uma_zfree_arg.9 \
Update and clean up the UMA man page. - Fix warnings from igor and mandoc. - Provide a brief description of the separation between zones and their backend slab allocators. - Document cache zones and secondary zones. - Document the kernel config options added in r350659. - Document the uma_zalloc_pcpu() and uma_zfree_pcpu() wrappers. - Document uma_zone_reserve(), uma_zone_reserve_kva() and uma_zone_prealloc(). - Document uma_zone_alloc() and uma_zone_freef(). - Add some missing MLINKs and Xrefs. MFC after: 2 weeks
2019-08-30 19:35:44 +00:00
zone.9 uma_zfree_pcpu.9 \
zone.9 uma_zfree_pcpu_arg.9 \
add a few missing links... Submitted by: J David MFC after: 1 week
2014-01-31 03:57:49 +00:00
zone.9 uma_zone_get_cur.9 \
zone.9 uma_zone_get_max.9 \
Extend uma_reclaim() to permit different reclamation targets. The page daemon periodically invokes uma_reclaim() to reclaim cached items from each zone when the system is under memory pressure. This is important since the size of these caches is unbounded by default. However it also results in bursts of high latency when allocating from heavily used zones as threads miss in the per-CPU caches and must access the keg in order to allocate new items. With r340405 we maintain an estimate of each zone's usage of its (per-NUMA domain) cache of full buckets. Start making use of this estimate to avoid reclaiming the entire cache when under memory pressure. In particular, introduce TRIM, DRAIN and DRAIN_CPU verbs for uma_reclaim() and uma_zone_reclaim(). When trimming, only items in excess of the estimate are reclaimed. Draining a zone reclaims all of the cached full buckets (the previous behaviour of uma_reclaim()), and may further drain the per-CPU caches in extreme cases. Now, when under memory pressure, the page daemon will trim zones rather than draining them. As a result, heavily used zones do not incur bursts of bucket cache misses following reclamation, but large, unused caches will be reclaimed as before. Reviewed by: jeff Tested by: pho (an earlier version) MFC after: 2 months Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D16667
2019-09-01 22:22:43 +00:00
zone.9 uma_zone_reclaim.9 \
Update and clean up the UMA man page. - Fix warnings from igor and mandoc. - Provide a brief description of the separation between zones and their backend slab allocators. - Document cache zones and secondary zones. - Document the kernel config options added in r350659. - Document the uma_zalloc_pcpu() and uma_zfree_pcpu() wrappers. - Document uma_zone_reserve(), uma_zone_reserve_kva() and uma_zone_prealloc(). - Document uma_zone_alloc() and uma_zone_freef(). - Add some missing MLINKs and Xrefs. MFC after: 2 weeks
2019-08-30 19:35:44 +00:00
zone.9 uma_zone_reserve.9 \
zone.9 uma_zone_reserve_kva.9 \
zone.9 uma_zone_set_allocf.9 \
zone.9 uma_zone_set_freef.9 \
Add missing mlinks for section 9. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
2014-09-22 13:04:49 +00:00
zone.9 uma_zone_set_max.9 \
Update and clean up the UMA man page. - Fix warnings from igor and mandoc. - Provide a brief description of the separation between zones and their backend slab allocators. - Document cache zones and secondary zones. - Document the kernel config options added in r350659. - Document the uma_zalloc_pcpu() and uma_zfree_pcpu() wrappers. - Document uma_zone_reserve(), uma_zone_reserve_kva() and uma_zone_prealloc(). - Document uma_zone_alloc() and uma_zone_freef(). - Add some missing MLINKs and Xrefs. MFC after: 2 weeks
2019-08-30 19:35:44 +00:00
zone.9 uma_zone_set_maxaction.9 \
zone.9 uma_zone_set_maxcache.9 \
Add a safety net to reclaim mbufs when one of the mbuf zones become exhausted. It is possible for a bug in the code (or, theoretically, even unusual network conditions) to exhaust all possible mbufs or mbuf clusters. When this occurs, things can grind to a halt fairly quickly. However, we currently do not call mb_reclaim() unless the entire system is experiencing a low-memory condition. While it is best to try to prevent exhaustion of one of the mbuf zones, it would also be useful to have a mechanism to attempt to recover from these situations by freeing "expendable" mbufs. This patch makes two changes: a) The patch adds a generic API to the UMA zone allocator to set a function that should be called when an allocation fails because the zone limit has been reached. Because of the way this function can be called, it really should do minimal work. b) The patch uses this API to try to free mbufs when an allocation fails from one of the mbuf zones because the zone limit has been reached. The function schedules a callout to run mb_reclaim(). Differential Revision: https://reviews.freebsd.org/D3864 Reviewed by: gnn Comments by: rrs, glebius MFC after: 2 weeks Sponsored by: Juniper Networks
2015-12-20 02:05:33 +00:00
zone.9 uma_zone_set_warning.9 \
Update and clean up the UMA man page. - Fix warnings from igor and mandoc. - Provide a brief description of the separation between zones and their backend slab allocators. - Document cache zones and secondary zones. - Document the kernel config options added in r350659. - Document the uma_zalloc_pcpu() and uma_zfree_pcpu() wrappers. - Document uma_zone_reserve(), uma_zone_reserve_kva() and uma_zone_prealloc(). - Document uma_zone_alloc() and uma_zone_freef(). - Add some missing MLINKs and Xrefs. MFC after: 2 weeks
2019-08-30 19:35:44 +00:00
zone.9 uma_zsecond_create.9
Add a man page for the zone allocator.
2001-01-27 19:13:08 +00:00
add superio.4 and superio.9 manual pages This adds basic documentation on what the superio driver is and how other drivers can interact with it. I decided to also document superio's ivar accessors. Reviewed by: bcr, brueffer (both manual contents only) MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D21958
2019-10-11 11:13:47 +00:00
.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386"
_superio.9= superio.9
MLINKS+=superio.9 superio_devid.9 \
superio.9 superio_dev_disable.9 \
superio.9 superio_dev_enable.9 \
superio.9 superio_dev_enabled.9 \
superio.9 superio_find_dev.9 \
superio.9 superio_find_dev.9 \
superio.9 superio_get_dma.9 \
superio.9 superio_get_iobase.9 \
superio.9 superio_get_irq.9 \
superio.9 superio_get_ldn.9 \
superio.9 superio_get_type.9 \
superio.9 superio_read.9 \
superio.9 superio_revid.9 \
superio.9 superio_vendor.9 \
superio.9 superio_write.9
.endif
Add a section 9 about the kernel to out man pages. Please help fill this out !
1995-12-14 10:08:31 +00:00
.include <bsd.prog.mk>
Reference in New Issue Copy Permalink