summaryrefslogtreecommitdiffstats
path: root/share/man
Commit message (Collapse)AuthorAgeFilesLines
* Document the new jail_reverse_stop parameterfeld2016-02-121-14/+16
| | | | | | | | | While here clean up the documentation for jail_list PR: 196152 Approved by: jamie, wblock MFC after: 1 week, with r295471 Differential Revision: https://reviews.freebsd.org/D5243
* Update .Dd for r295565bjk2016-02-121-1/+1
|
* Clarify the difference between 7- and 8-bit i2c addresses, used in FDTian2016-02-121-4/+7
| | | | | | versus hints-based configuration, respectively. Reported by: Jukka Ukkonen <jau789@gmail.com>
* Explain that boot1.efi prefers ZFS over UFSemaste2016-02-111-0/+7
| | | | Reported by: smh
* Update uefi.8 for ZFS and multi device boot supportemaste2016-02-111-19/+11
| | | | | | | | | | As of r294068 boot1.efi can load loader.efi from ZFS. As of r295320 boot1.efi prefers to load loader.efi from the same device it was loaded from. MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Document boot1.efi's handling of /boot.config, added in r294768emaste2016-02-111-1/+12
| | | | | MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Simplify running the FreeBSD test suitengie2016-02-071-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace `make regress` (legacy test make target) and `make test` (incomplete test make target added with the FreeBSD test suite) with make check as it's consistent with other open source projects. `make check` defaults to running tests from `.OBJDIR`, but can be overridden with the `CHECKDIR` variable. Add `make checkworld` target to simplify running the FreeBSD test suite from `TESTSBASE` (i.e. the top-level tests directory), similar to buildworld. Document `make check` and `make checkworld` in build(7). Other minor changes: - Rename intermediate file (`Kyuafile.auto`) to `Kyuafile` to simplify `make check`. - Remove terse warnings attached to `beforetest`/`aftertest`. - Add kyua binary check to check target in suite.test.mk; error out if it's not found The MFC is [partly] contingent on other build related changes being MFCed. Differential Revision: https://reviews.freebsd.org/D4406 MFC after: 2 months X-MFC to: stable/10 Relnotes: yes Reviewed by: bdrewery, Evan Cramer <eccramer@gmail.com> Sponsored by: EMC / Isilon Storage Division
* Add missing commadteske2016-02-071-2/+2
|
* Summary: Update the dategnn2016-02-041-1/+1
|
* Summary: Remove discussion of fastforwarding.gnn2016-02-041-23/+1
|
* Note the double fork behavior with filemon.bdrewery2016-01-291-0/+5
| | | | | | X-MFC-With: r295029 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
* Document the purpose and non-purpose of filemon(4).bdrewery2016-01-291-1/+17
| | | | | MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
* nvd: add hw.nvd.delete_max tunablejimharris2016-01-281-2/+11
| | | | | | | | | | | | | | | The NVMe specification does not define a maximum or optimal delete size, so technically max delete size is min(full size of namespace, 2^32 - 1 LBAs). A single delete operation for a multi-TB NVMe namespace though may take much longer to complete than the nvme(4) I/O timeout period. So choose a sensible default here that is still suitably large to minimize the number of overall delete operations. This also fixes possible uint32_t overflow on initial TRIM operation for zpool create operations for NVMe namespaces with >4G LBAs. MFC after: 3 days Sponsored by: Intel
* Rename netinet/tcp_cc.h to netinet/cc/cc.h.glebius2016-01-271-1/+1
| | | | Discussed with: lstewart
* Convert rman to use rman_res_t instead of u_longjhibbits2016-01-275-14/+18
| | | | | | | | | | | | | | | | | | | | Summary: Migrate to using the semi-opaque type rman_res_t to specify rman resources. For now, this is still compatible with u_long. This is step one in migrating rman to use uintmax_t for resources instead of u_long. Going forward, this could feasibly be used to specify architecture-specific definitions of resource ranges, rather than baking a specific integer type into the API. This change has been broken out to facilitate MFC'ing drivers back to 10 without breaking ABI. Reviewed By: jhb Sponsored by: Alex Perez/Inertial Computing Differential Revision: https://reviews.freebsd.org/D5075
* Document that hashinit(9) can wait for memory to be availablebjk2016-01-231-2/+4
| | | | | | Also tweak nearby grammar while here. Submitted by: Daniel O'Connor (original version)
* Advertise support for ext3 and ext4.trasz2016-01-231-3/+9
| | | | | MFC after: 1 month Sponsored by: The FreeBSD Foundation
* Add an IOCTL rr_limit to let users fine tuning the number of packets to bearaujo2016-01-231-1/+19
| | | | | | | | | | | | | | | | | | | sent using roundrobin protocol and set a better granularity and distribution among the interfaces. Tuning the number of packages sent by interface can increase throughput and reduce unordered packets as well as reduce SACK. Example of usage: # ifconfig bge0 up # ifconfig bge1 up # ifconfig lagg0 create # ifconfig lagg0 laggproto roundrobin laggport bge0 laggport bge1 \ 192.168.1.1 netmask 255.255.255.0 # ifconfig lagg0 rr_limit 500 Reviewed by: thompsa, glebius, adrian (old patch) Approved by: bapt (mentor) Relnotes: Yes Differential Revision: https://reviews.freebsd.org/D540
* Provide new socket option TCP_CCALGOOPT, which stands for TCP congestionglebius2016-01-223-5/+36
| | | | | | | | | | | | | | | control algorithm options. The argument is variable length and is opaque to TCP, forwarded directly to the algorithm's ctl_output method. Provide new includes directory netinet/cc, where algorithm specific headers can be installed. The new API doesn't yet have any in tree consumers. The original code written by lstewart. Reviewed by: rrs, emax Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D711
* Add a simple manpage for the cfi(4) and associated cfid(4) drivers.brooks2016-01-202-0/+96
| | | | | MFC after: 1 week Sponsored by: DARPA, AFRL
* Add vrefl(), a locked variant of vref(9).markj2016-01-181-3/+12
| | | | | | | | | | | This API has no in-tree consumers at the moment but is useful to at least one out-of-tree consumer, and naturally complements existing vnode refcount functions (vholdl(9), vdropl(9)). Obtained from: kib (sys/ portion) Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D4947 Differential Revision: https://reviews.freebsd.org/D4953
* mdoc: sort Xrjoel2016-01-181-1/+1
|
* Bump .Dd for the content changesngie2016-01-161-1/+1
|
* trim-time? What was I thinking. run-time.imp2016-01-161-1/+1
| | | | Noticed by: Allan Jude
* Add some clarifications.imp2016-01-161-4/+9
|
* Improve the sentence flow as well which has the happy benefit ofimp2016-01-161-2/+2
| | | | | making read-only modify a noun, a case where it unquestionably should be hyphenated.
* Although not directly modifying a noun, read-only should be hyphenatedimp2016-01-161-2/+2
| | | | in this context (or in any, really).
* Read-only is typically hyphenated. Move (read only) to a spot where itimp2016-01-161-1/+1
| | | | modifies a noun and hyphenate.
* Read-only is hyphenated when it modifies a noun.imp2016-01-165-8/+8
|
* sfxge: support FATSOv2arybchik2016-01-151-2/+4
| | | | | | | Reviewed by: gnn Sponsored by: Solarflare Communications, Inc. MFC after: 2 days Differential Revision: https://reviews.freebsd.org/D4934
* ioat(4): Add support for 'fence' bit with DMA_FENCE flagcem2016-01-151-2/+13
| | | | | | | | | | | Some classes of IOAT hardware prefetch reads. DMA operations that depend on the result of prior DMA operations must use the DMA_FENCE flag to prevent stale reads. (E.g., I've hit this personally on Broadwell-EP. The Broadwell-DE has a different IOAT unit that is documented to not pipeline DMA operations.) Sponsored by: EMC / Isilon Storage Division
* Fix spelling of IPMIngie2016-01-141-1/+1
| | | | Sponsored by: EMC / Isilon Storage Division
* Update .Dd, missed in r294011bjk2016-01-141-1/+1
|
* Document how to enter the debugger here. I'm sure there's some betterimp2016-01-141-0/+41
| | | | | | | canonical place, and the nit-pickers are welcome to move this information there with a cross reference. Differential Review: https://reviews.freebsd.org/D4860
* Restore uart PPS signal capture polarity to its historical norm, and add anian2016-01-121-6/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | option to invert the polarity in software. Also add an option to capture very narrow pulses by using the hardware's MSR delta-bit capability of latching line state changes. This effectively reverts the mistake I made in r286595 which was based on empirical measurements made on hardware using TTL-level signaling, in which the logic levels are inverted from RS-232. Thus, this re-syncs the polarity with the requirements of RFC 2783, which is writen in terms of RS-232 signaling. Narrow-pulse mode uses the ability of most ns8250 and similar chips to provide a delta indication in the modem status register. The hardware is able to notice and latch the change when the pulse width is shorter than interrupt latency, which results in the signal no longer being asserted by time the interrupt service code runs. When running in this mode we get notified only that "a pulse happened" so the driver synthesizes both an ASSERT and a CLEAR event (with the same timestamp for each). When the pulse width is about equal to the interrupt latency the driver may intermittantly see both edges of the pulse. To prevent generating spurious events, the driver implements a half-second lockout period after generating an event before it will generate another. Differential Revision: https://reviews.freebsd.org/D4477
* Update ismt(4) man page to reflect inclusion in upcoming 10.3 release.jimharris2016-01-111-2/+2
| | | | | MFC after: 3 days Sponsored by: Intel
* Regen after r293450emaste2016-01-091-1/+22
|
* Fix issues found by mandoc -Tlint.brueffer2016-01-084-6/+4
| | | | MFC after: 1 week
* ioat(4): Add ioat_acquire_reserve() KPIcem2016-01-071-1/+11
| | | | | | | | | ioat_acquire_reserve() is an extended version of ioat_acquire(). It allows users to reserve space in the channel for some number of descriptors. If this succeeds, it guarantees that at least submission of N valid descriptors will succeed. Sponsored by: EMC / Isilon Storage Division
* nvme: add hw.nvme.min_cpus_per_ioq tunablejimharris2016-01-071-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | Due to FreeBSD system-wide limits on number of MSI-X vectors (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321), it may be desirable to allocate fewer than the maximum number of vectors for an NVMe device, in order to save vectors for other devices (usually Ethernet) that can take better advantage of them and may be probed after NVMe. This tunable is expressed in terms of minimum number of CPUs per I/O queue instead of max number of queues per controller, to allow for a more even distribution of CPUs per queue. This avoids cases where some number of CPUs have a dedicated queue, but other CPUs need to share queues. Ideally the PR referenced above will eventually be fixed and the mechanism implemented here becomes obsolete anyways. While here, fix a bug in the CPUs per I/O queue calculation to properly account for the admin queue's MSI-X vector. Reviewed by: gallatin MFC after: 3 days Sponsored by: Intel
* Provide yet another KPI for cdev creation, make_dev_s(9).kib2016-01-072-47/+136
| | | | | | | | | | | | | | | | | | | 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
* Use standard name for ASCII LF and FF control codesemaste2016-01-061-4/+4
| | | | | PR: 205778 MFC after: 2 weeks
* ioat(4): Add ioat_get_max_io_size() KPIcem2016-01-051-1/+3
| | | | | | | Consumers need to know the permitted IO size to send maximally sized chunks to the hardware. Sponsored by: EMC / Isilon Storage Division
* 17 years and change after I wrote warp_saver, here's a simple plasma effectdes2016-01-011-1/+11
| | | | | (currently only three circular patterns) which requires quite a bit of fixed-point arithmetic, including sqrt() and cos(). Happy New Year!
* [rtwn] Add initial manpages for the rtwn driver.adrian2015-12-313-0/+241
|
* procfs(5) is not required by ps(1) and w(1) anymorebapt2015-12-261-6/+2
| | | | Remove references of those tools in procfs(5)
* [mdio] migrate mdiobus out of etherswitch and into a top-level device of its ↵adrian2015-12-262-0/+54
| | | | | | | | | | | own. The mdio driver interface is generally useful for devices that require MDIO without the full MII bus interface. This lifts the driver/interface out of etherswitch(4), and adds a mdio(4) man page. Submitted by: Landon Fuller <landon@landonf.org> Differential Revision: https://reviews.freebsd.org/D4606
* Add accessor methods to fetch the BAR holding the MSI-X table and PBA.jhb2015-12-232-3/+54
| | | | | | | | | 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
* Add a safety net to reclaim mbufs when one of the mbuf zones becomejtl2015-12-202-4/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* ioat(4): Add an API to get HW revisioncem2015-12-171-1/+3
| | | | | | | | Different revisions support different operations. Refer to Intel External Design Specifications to figure out what your hardware supports. Sponsored by: EMC / Isilon Storage Division
OpenPOWER on IntegriCloud