path: root/share/man
Commit message (Collapse)AuthorAgeFilesLines
* pci: Disable Electromechanical Interlock.Alexander Motin5 hours1-1/+3
| | | | | | | | | | | | | Add sysctl/tunable to control Electromechanical Interlock support. Disable it by default since Linux does not do it either and it seems the number of systems having it broken is higher than having working. This fixes NVMe backplane operation on ASUS RS500A-E11-RS12U server with AMD EPYC 7402 CPU, where attempts to control reported interlock for some reason end up in PCIe link loss, while interlock status does not change (it is not really there). MFC after: 2 weeks
* tcp: allow window scale and timestamps to be toggled individuallyRichard Scheffenegger26 hours1-1/+12
| | | | | | | | | Simple change to allow for the individual toggling of RFC7323 window scaling and timestamp option. Reviewed By: rrs, tuexen, glebius, guest-ccui, #transport Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D36863
* rb_tree: let insert search start from next nodeDoug Moore40 hours1-0/+18
| | | | | | | | | | | | | | | When the node to insert in the rb_tree is known to precede or follow a particular node, new methods RB_INSERT_PREV and RB_INSERT_NEXT, defined here, allow the search for where to insert the new node begin with that particular node, rather than at the root, to save a bit of time. Using those methods, instead of RB_INSERT, in managing a tree in iommu_gas.c, saves a little time. Reviewed by: kib MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D35516
* manpages: Remove telnetd referencesBrooks Davis5 days2-9/+8
| | | | | | | | | | Mostly remove from the SEE ALSO section, adding a mention of the port where not removed. Elsewhere, remove as appropriate and change from .Xr to .Nm where a mention of telnetd continues to make sense (or removing it would require significant reworking of the surrounding text). Reviewed by: imp, delphij, emaste Differential Revision: https://reviews.freebsd.org/D36785
* Tcp progress timeoutRandall Stewart7 days1-0/+12
| | | | | | | | | | | Rack has had the ability to timeout connections that just sit idle automatically. This feature of course is off by default and requires the user set it on (though the socket option has been missing in tcp_usrreq.c). Lets get the progress timeout fully supported in the base stack as well as rack. Reviewed by: tuexen Sponsored by: Netflix Inc Differential Revision: https://reviews.freebsd.org/D36716
* man9: Add MLINKs for bus_space_{peek,poke}Mark Johnston8 days1-0/+8
| | | | MFC after: 1 week
* snp(4): implement detachKonstantin Belousov9 days1-6/+0
| | | | | | | | | PR: 257964 Reported by: Bertrand Petit <bsdpr@phoe.frmug.org> Reviewed by: imp, markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D36690
* snp(4): properly report detached/revoked ttysKonstantin Belousov9 days1-6/+2
| | | | | | | | | PR: 257964 Reported by: Bertrand Petit <bsdpr@phoe.frmug.org> Reviewed by: imp, markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D36690
* cpuset(9): Refer to CPU_SETSIZE not MAXCPUBrooks Davis11 days1-3/+3
| | | | | | | | | | | | | | The maximum CPU number of a cpuset_t is determined by CPU_SETSIZE. In the kernel this is MAXCPU, but in userspace it is CPU_MAXSIZE unless CPU_SETSIZE is defined before including sys/_cpuset.h. CPU_MAXSIZE is 256 and in userspace MAXCPU is generally 1 because it being set to a larger MD value is gated on SMP being defined (not generally the case in userspace). Reported by: Nathaniel Wesley Filardo <nwfilardo@gmail.com> Reviewed by: cem, jhb MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D36679
* iwlwifi.4: typo fixedMaxim Konovalov12 days1-1/+1
| | | | PR: 266554
* rb_tree: augmentation shortcutDoug Moore14 days2-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | RB-tree augmentation maintains data in each node of the tree that represents the product of some associative operator applied to all the nodes of the subtree rooted at that node. If a node in the tree changes, augmentation data for the node is updated for that node and all nodes on the path from that node to the tree root. However, sometimes, augmenting a node changes no data in that node, particularly if the associated operation is something involving 'max' or 'min'. If augmentation changes nothing in a node, then the work of walking to the tree root from that point is pointless, because augmentation will change nothing in those nodes either. This change makes it possible to avoid that wasted work. Define RB_AUGMENT_CHECK as a macro much like RB_AUGMENT, but which returns a value 'true' when augmentation changes the augmentation data of a node, and false otherwise. Change code that unconditionally walks and augments to the top of tree to code that stops once an augmentation has no effect. In the case of rebalancing the tree after insertion or deletion, where previously a node rotated into the path was inevitably augmented on the march to the tree root, now check to see if it needs augmentation because the march to the tree root stopped before reaching it. Change the augmentation function in iommu_gas.c so that it returns true/false to indicate whether the augmentation had any effect. Reviewed by: alc, kib MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D36509
* linuxkpi: drm-kmod debugfs supportJake Freeland2022-09-202-0/+96
| | | | | | | | | | | | This diff extends LinuxKPI to support simple attribute files in debugfs. These simple attributes are an essential component for compiling drm-kmod with CONFIG_DEBUG_FS enabled. This will allow for easier graphics driver debugging using Intel's igt-gpu-tools. Reviewed by: hselasky Differential Revision: https://reviews.freebsd.org/D35883 Sponsored by: Google, Inc. (GSoC 2022)
* Fix dead references (wrong section) to sysctl(8).Jens Schweikhardt2022-09-161-1/+1
* bridge.4: describe new MTU behaviourKristof Provost2022-09-161-3/+6
| | | | | | | | | | | 1865ebfb12 changed if_bridge to have it change the MTU on newly added interfaces to match the if_bridge MTU, rather than rejecting them for having an incorrect MTU. Update the man page to reflect this, as pointed out by woodsb02. Reviewed by: woodsb02 Differential Revision: https://reviews.freebsd.org/D36481
* arch: armv4 isn't supported either on aarch64 running in aarch32 modeWarner Losh2022-09-151-2/+4
| | | | | | | | | | FreeBSD used to support both armv4 and armv5 binaries. All of that support has been removed from the tree. We have only ever supported armv6 and armv7 binaries in that mode. Note armv4 here too for completeness since it flowed better than 'armv5 and earlier' and means the same thing (FreeBSD never ran on an armv3 or earlier CPU). Sponsored by: Netflix
* Update SEE ALSO sections for resolver.{3,5} and hosts.5Gordon Bergling2022-09-152-8/+2
| | | | | | | | | | | | The mentioned document "Name Server Operations Guide for BIND" is outdated, so remove it from the SEE ALSO section of hosts.5 and resolver.{3,5}. PR: 266360 Reported by: Graham Perrin <grahamperrin at FreeBSD dot org> Reviewed by: karels MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D36557
* Unbreak the build after b3ee318b79d54a59190d35b8c76a63a8fb81b903Mateusz Guzik2022-09-141-1/+1
* domains: rewrite documentation to describe present stateGleb Smirnoff2022-09-142-179/+160
| | | | | Reviewed by: debdrup, pauamma Differential revision: https://reviews.freebsd.org/D36513
* tcp: make CUBIC the default congestion control mechanism.Richard Scheffenegger2022-09-133-10/+10
| | | | | | | | | | | | | This changes the default TCP Congestion Control (CC) to CUBIC. For small, transactional exchanges (e.g. web objects <15kB), this will not have a material effect. However, for long duration data transfers, CUBIC allocates a slightly higher fraction of the available bandwidth, when competing against NewReno CC. Reviewed By: tuexen, mav, #transport, guest-ccui, emaste Relnotes: Yes Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D36537
* cxgbe(4): Add another setting to the knob that controls congestion.Navdeep Parhar2022-09-121-1/+2
| | | | | | | | hw.cxgbe.cong_drop=2 will generate backpressure *and* drop frames for queues that are congested. MFC after: 2 weeks Sponsored by: Chelsio Communications
* da.4: Don't document softtimeoutWarner Losh2022-09-101-7/+0
| | | | | | | | | | | | | | | | kern.cam.da.default_softtimeout currently does nothing. It sets a value in the CCB that SIMs could look at, only none do. Leave it undocumented until it actually does something. It was introduced to allow a 'soft recovery' to be started when things were taking too long in the SIM by not scheduling new I/O, or other measures the SIM knew would help when it seemed like things were getting 'backed up'. No SIM in the FreeBSD tree implements this and scsi_da doesn't use it other than to pass it down, so best remove it from the documentation until it does something. Sponsored by: Netflix Fixes: 53af9c235f5d Reviewed by: gbe Differential Review: https://reviews.freebsd.org/D36518
* da.4: Add some sysctl descriptionsFelix Johnson2022-09-101-9/+40
| | | | | | | | | | | | | | | | | | | Add descriptions for the following sysctl's: - kern.cam.da.default_softtimeout - kern.cam.da.disable_wp_protection - kern.cam.da.enable_biospeedup - kern.cam.da.enable_uma_ccbs - kern.cam.da.poll_period - kern.cam.da.send_ordered While here, fix some mandocs warnings. PR: 258727 Reported by: Felix Johnson <felix dot the dot red at gmail dot com> Reviewed by: debdrup, pauamma, gbe MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D32278
* ifnet(9): Duplicates for IFCAP_TOE flags removed.Maxim Konovalov2022-09-101-9/+2
| | | | PR: 266330
* src.conf.5: Regenerate.Gleb Popov2022-09-091-5/+5
| | | | | Approved by: imp Fixes: 20adba8bc1beb125d5e5ed8f12e747ae79ca6a10
* src.conf: Introduce WITHOUT_MACHDEP knob.Gleb Popov2022-09-091-0/+2
| | | | | | | | | | | | | | Summary: This knob can be used to make buildsystem prefer generic C implentations of various functions, instead of machine-specific assembler ones. Test Plan: `make buildworld` on amd64 Reviewed by: imp, emaste Differential Revision: https://reviews.freebsd.org/D36076 MFC after: 3 days
* ip_reass: add loader tunable to tune the reassembly hash sizeGleb Smirnoff2022-09-081-0/+2
* ip_reass: retire ipreass_slowtimo() in favor of per-slot calloutGleb Smirnoff2022-09-081-1/+3
| | | | | | | | | | | o Retire global always running ipreass_slowtimo(). o Instead use one callout entry per hash slot. The per-slot callout would be scheduled only if a slot has entries, and would be driven by TTL of the very last entry. o Make net.inet.ip.fragttl read/write and document it. o Retire IPFRAGTTL, which used to be meaningful only with PR_SLOWTIMO. Differential revision: https://reviews.freebsd.org/D36275
* libexec/rc: Add var_run rc scriptCy Schubert2022-09-051-0/+28
| | | | | | | | | | | | | | | | | | Users with a tmpfs /var/run will lose the directory tree state of /var/run at reboot. This rc script will optionally (by default) capture the state of the directory structure in /var/run prior to shutdown and recreate it at system boot. Alternatively a user can save the state of the /var/run directories manually using service var_run save and disable the autosaving of /var/run state using the var_run_autosave variable, for those paranoid SSD users. PR: 259585, 259699 Reported by: freebsd@walstatt-de.de, Reviewed by: philip, gbe (previous version) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D36386
* ip6.4: Correct a typo in the manual pageGordon Bergling2022-09-041-1/+1
| | | | | | - s/the the/the/ MFC after: 3 days
* tcp: Functional implementation of Accurate ECNRichard Scheffenegger2022-08-311-0/+7
| | | | | | | | | | | | The AccECN handshake and TCP header flags are supported, no support yet for the AccECN option. This minimalistic implementation is sufficient to support DCTCP while dramatically cutting the number of ACKs, and provide ECN response from the receiver to the CC modules. Reviewed By: #transport, #manpages, rrs, pauamma Sponsored by: NetApp, Inc. Differential Revision: https://reviews.freebsd.org/D21011
* divert(4): maintain own cb database and stop using inpcb KPIGleb Smirnoff2022-08-301-3/+2
| | | | | | | | | | | | | | | | | | | | Here go cons of using inpcb for divert: - divert(4) uses only 16 bits (local port) out of struct inpcb, which is 424 bytes today. - The inpcb KPI isn't able to provide hashing for divert(4), thus it uses global inpcb list for lookups. - divert(4) uses INET-specific part of the KPI, making INET a requirement for IPDIVERT. Maintain our own very simple hash lookup database instead. It has mutex protection for write and epoch protection for lookups. Since now so->so_pcb no longer points to struct inpcb, don't initialize protosw methods to methods that belong to PF_INET. Also, drop support for setting options on a divert socket. My review of software in base and ports confirms that this has no use and unlikely worked before. Differential revision: https://reviews.freebsd.org/D36382
* divert: declare PF_DIVERT domain and stop abusing PF_INETGleb Smirnoff2022-08-301-15/+23
| | | | | | | | | | | | | | | | | | | | | | | | | The divert(4) is not a protocol of IPv4. It is a socket to intercept packets from ipfw(4) to userland and re-inject them back. It can divert and re-inject IPv4 and IPv6 packets today, but potentially it is not limited to these two protocols. The IPPROTO_DIVERT does not belong to known IP protocols, it doesn't even fit into u_char. I guess, the implementation of divert(4) was done the way it is done basically because it was easier to do it this way, back when protocols for sockets were intertwined with IP protocols and domains were statically compiled in. Moving divert(4) out of inetsw accomplished two important things: 1) IPDIVERT is getting much closer to be not dependent on INET. This will be finalized in following changes. 2) Now divert socket no longer aliases with raw IPv4 socket. Domain/proto selection code won't need a hack for SOCK_RAW and multiple entries in inetsw implementing different flavors of raw socket can merge into one without requirement of raw IPv4 being the last member of dom_protosw. Differential revision: https://reviews.freebsd.org/D36379
* rc.conf(5): add <service>_umask to run the service using this valueEugene Grosbein2022-08-281-1/+7
| | | | | | | | | | | None of tools working with login classes change umask(1) and we had no ways to specify non-default umask for a service not touching its startup script. This change makes in possible. Some file-sharing services that create new files may benefit from it. Differential: https://reviews.freebsd.org/D36309 MFC-after: 3 days
* m_get3: add an MLINK for the manpageBrooks Davis2022-08-231-0/+1
| | | | | | Reviewed by: kp Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D36319
* vfs: fix vaccess prototype in the manpageMateusz Guzik2022-08-231-15/+4
| | | | Reported by: des
* vfs: fix VOP_UNLOCK prototype in the manpageMateusz Guzik2022-08-231-2/+2
| | | | | | Note the manpage is woefully outdated, taking about "simple lock". Reported by: des
* kqueue: retire knlist_init_rw_reader()Robert Wing2022-08-212-21/+4
| | | | | | | Last usage was removed in afa85850e79c1839ec33efa1138206687b952cfa. Reviewed by: pauamma, melifaro, kib Differential Revision: https://reviews.freebsd.org/D36205
* development(7): Update URLsLi-Wen Hsu2022-08-181-5/+5
| | | | | MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Indicate which port gdb.1 and kgdb.1 come from.Jens Schweikhardt2022-08-179-20/+20
* Indicate that xrefs to *roff,tbl,eqn et al are found in ports/textproc/groff.Jens Schweikhardt2022-08-151-1/+1
* Indicate that kgdb.1 is from ports/devel/gdb.Jens Schweikhardt2022-08-144-7/+7
* For man page references found in ports, indicate the respective port.Jens Schweikhardt2022-08-141-1/+1
* Indicate that X(7) cross refs are satisfied by ports/x11/xorg-docs.Jens Schweikhardt2022-08-146-7/+7
* Fix wrong capitalization in man page references.Jens Schweikhardt2022-08-134-6/+7
* Fix a broken man page reference.Jens Schweikhardt2022-08-131-1/+1
* rtw88: correct a typo in man pageAndres Ramirez2022-08-071-2/+2
| | | | | | s/mmeory/memory/ MFC after: 1 week
* tree.3: explain RB_FIND() and RB_NFIND()Konstantin Belousov2022-08-071-1/+16
| | | | | | | | In collaboration with: dougm Reviewed by: alc Sponsored by: The FreeBSD Foundation (kib) MFC after: 3 days Differential revision: https://reviews.freebsd.org/D36001
* tree.3: fix markupKonstantin Belousov2022-08-071-1/+3
| | | | | | | Reviewed by: alc, dougm Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential revision: https://reviews.freebsd.org/D36001
* hier.7: Document /var/db/freebsd-updateMateusz Piotrowski2022-08-041-1/+6
| | | | | MFC after: 3 days Sponsored by: Klara, Inc.
* rb_tree: update augmentation after element changeDoug Moore2022-08-021-4/+20
| | | | | | | | | | | | | For an augmented rb_tree, allow a faster alternative to removing an element from the tree, tweaking it slightly, and inserting it back into the tree, knowing that its relative position in the tree is unchanged. Instead, just change the element and invoke RB_UPDATE_AUGMENT to fix the augmentation data for all the nodes in the tree. Reviewed by: kib MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D36010