summaryrefslogtreecommitdiffstats
path: root/share/man
Commit message (Collapse)AuthorAgeFilesLines
* Few more minor if_vmx tweaksbryanv2013-08-301-1/+20
| | | | | | | - Allow the Rx/Tx queue sizes to be configured by tunables - Bail out earlier if the Tx queue unlikely has enough free descriptors to hold the frame - Cleanup some of the offloading capabilities handling
* Fix after r255014antoine2013-08-291-4/+1
|
* Add a simple procdesc(4) man page describing "options PROCDESC" and therwatson2013-08-283-5/+103
| | | | | | | | high-level facility, supplementing pdfork(2) and friends. Update capsicum.4 to xref. Suggested by: sbruno MFC after: 3 days
* mdoc fixjoel2013-08-281-1/+1
|
* Really regen after r254962.zeising2013-08-271-7/+4
| | | | | | | This removes the WITH_BSDCONFIG description alltogether, since this option is removed. At the same time, fix the WITHOUT_LIBCPLUSPLUS option that had gotten inverted.
* Make the period of each periodic security script configurable.jlh2013-08-271-18/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are now six additional variables weekly_status_security_enable weekly_status_security_inline weekly_status_security_output monthly_status_security_enable monthly_status_security_inline monthly_status_security_output alongside their existing daily counterparts. They all have the same default values. All other "daily_status_security_${scriptname}_${whatever}" variables have been renamed to "security_status_${name}_${whatever}". A compatibility shim has been introduced for the old variable names, which we will be able to remove in 11.0-RELEASE. "security_status_${name}_enable" is still a boolean but a new "security_status_${name}_period" allows to define the period of each script. The value is one of "daily" (the default for backward compatibility), "weekly", "monthly" and "NO". Note that when the security periodic scripts are run directly from crontab(5) (as opposed to being called by daily or weekly periodic scripts), they will run unless the test is explicitely disabled with a "NO", either for in the "_enable" or the "_period" variable. When the security output is not inlined, the mail subject has been changed from "$host $arg run output" to "$host $arg $period run output". For instance: myfbsd security run output -> myfbsd security daily run output I don't think this is considered as a stable API, but feel free to correct me if I'm wrong. Finally, I will rearrange periodic.conf(5) and default/periodic.conf to put the security options in their own section. I left them in place for this commit to make reviewing easier. Reviewed by: hackers@
* Formally remove WITH_BSDCONFIG build option and re-generate src.conf.5dteske2013-08-271-4/+4
| | | | NOTE: Should have been inline with revisions 252862 and 254958.
* fix up my copyright..jmg2013-08-261-2/+1
|
* none of the drivers in the tree support CDIOCCAPABILITY or CDIOCPITCH..jmg2013-08-261-81/+0
| | | | | remove the documentation so people won't get confused and think they are supported...
* Regenerate src.conf.5antoine2013-08-261-7/+19
|
* Hook vm_page_busy.9 to the buildantoine2013-08-261-0/+1
|
* Remove EOL whitespace.joel2013-08-251-1/+1
|
* mdoc fixes.joel2013-08-251-1/+2
|
* Fix BUGS section after botched modify in r254772.andre2013-08-241-2/+1
| | | | Reported by: bjk
* Rename the kld_unload event handler to kld_unload_try, and add a newmarkj2013-08-241-0/+2
| | | | | | | | | | | | | | kld_unload event handler which gets invoked after a linker file has been successfully unloaded. The kld_unload and kld_load event handlers are now invoked with the shared linker lock held, while kld_unload_try is invoked with the lock exclusively held. Convert hwpmc(4) to use these event handlers instead of having kern_kldload() and kern_kldunload() invoke hwpmc(4) hooks whenever files are loaded or unloaded. This has no functional effect, but simplifes the linker code somewhat. Reviewed by: jhb
* Adjust for the pfil_func_t typedef added in r254769.andre2013-08-241-4/+4
|
* pfil_hook_get() has been internalized in r254771 and is no longerandre2013-08-241-9/+2
| | | | part of the API. It wasn't safe for external use in any case.
* Add support to physio(9) for devices that don't want I/O split andken2013-08-241-1/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configure sa(4) to request no I/O splitting by default. For tape devices, the user needs to be able to clearly understand what blocksize is actually being used when writing to a tape device. The previous behavior of physio(9) was that it would split up any I/O that was too large for the device, or too large to fit into MAXPHYS. This means that if, for instance, the user wrote a 1MB block to a tape device, and MAXPHYS was 128KB, the 1MB write would be split into 8 128K chunks. This would be done without informing the user. This has suboptimal effects, especially when trying to communicate status to the user. In the event of an error writing to a tape (e.g. physical end of tape) in the middle of a 1MB block that has been split into 8 pieces, the user could have the first two 128K pieces written successfully, the third returned with an error, and the last 5 returned with 0 bytes written. If the user is using a standard write(2) system call, all he will see is the ENOSPC error. He won't have a clue how much actually got written. (With a writev(2) system call, he should be able to determine how much got written in addition to the error.) The solution is to prevent physio(9) from splitting the I/O. The new cdev flag, SI_NOSPLIT, tells physio that the driver does not want I/O to be split beforehand. Although the sa(4) driver now enables SI_NOSPLIT by default, that can be disabled by two loader tunables for now. It will not be configurable starting in FreeBSD 11.0. kern.cam.sa.allow_io_split allows the user to configure I/O splitting for all sa(4) driver instances. kern.cam.sa.%d.allow_io_split allows the user to configure I/O splitting for a specific sa(4) instance. There are also now three sa(4) driver sysctl variables that let the users see some sa(4) driver values. kern.cam.sa.%d.allow_io_split shows whether I/O splitting is turned on. kern.cam.sa.%d.maxio shows the maximum I/O size allowed by kernel configuration parameters (e.g. MAXPHYS, DFLTPHYS) and the capabilities of the controller. kern.cam.sa.%d.cpi_maxio shows the maximum I/O size supported by the controller. Note that a better long term solution would be to implement support for chaining buffers, so that that MAXPHYS is no longer a limiting factor for I/O size to tape and disk devices. At that point, the controller and the tape drive would become the limiting factors. sys/conf.h: Add a new cdev flag, SI_NOSPLIT, that allows a driver to tell physio not to split up I/O. sys/param.h: Bump __FreeBSD_version to 1000049 for the addition of the SI_NOSPLIT cdev flag. kern_physio.c: If the SI_NOSPLIT flag is set on the cdev, return any I/O that is larger than si_iosize_max or MAXPHYS, has more than one segment, or would have to be split because of misalignment with EFBIG. (File too large). In the event of an error, print a console message to give the user a clue about what happened. scsi_sa.c: Set the SI_NOSPLIT cdev flag on the devices created for the sa(4) driver by default. Add tunables to control whether we allow I/O splitting in physio(9). Explain in the comments that allowing I/O splitting will be deprecated for the sa(4) driver in FreeBSD 11.0. Add sysctl variables to display the maximum I/O size we can do (which could be further limited by read block limits) and the maximum I/O size that the controller can do. Limit our maximum I/O size (recorded in the cdev's si_iosize_max) by MAXPHYS. This isn't strictly necessary, because physio(9) will limit it to MAXPHYS, but it will provide some clarity for the application. Record the controller's maximum I/O size reported in the Path Inquiry CCB. sa.4: Document the block size behavior, and explain that the option of allowing physio(9) to split the I/O will disappear in FreeBSD 11.0. Sponsored by: Spectra Logic
* Remove duplicate copy of the man pagebryanv2013-08-231-112/+0
| | | | Pointed out by: jmallett
* Add vmx(4), a VMware VMXNET3 ethernet driver ported from OpenBSDbryanv2013-08-232-0/+228
|
* - Bump date.davide2013-08-231-2/+2
| | | | | | - Small mdoc fix. Submitted by: pluknet
* Introduce callout_init_rm() so that callouts can be used in conjunctiondavide2013-08-231-6/+20
| | | | | | | | | with rmlocks. This works only with non-sleepable rm because handlers run in SWI context. While here, document the new KPI in the timeout(9) manpage. Requested by: adrian, scottl Reviewed by: mav, remko(manpage)
* Update the manual page for vm_page_grab(9).kib2013-08-221-13/+27
| | | | | Reviewed and edited by: alc Sponsored by: The FreeBSD Foundation
* Minor mdoc nit.joel2013-08-221-1/+0
|
* Implement atomic_swap() and atomic_testandset().jkim2013-08-211-17/+66
| | | | Reviewed by: arch, bde, jilles, kib
* Update the SDT(9) man page with the macros added in 254468. Also change themarkj2013-08-171-10/+79
| | | | | | | | existing examples to not pass an mbuf as a probe argument. There's no obvious reason to have it there, and it doesn't really jibe with the example added in this revision. MFC after: 1 week
* Correct sentence syntax too.mjacob2013-08-171-3/+3
|
* Correct spelling.obrien2013-08-171-1/+1
|
* Bring datasheet URL up to date.kevlo2013-08-161-1/+1
|
* Fix a typo.markj2013-08-151-1/+1
| | | | MFC after: 3 days
* Remove the {SRC,DOC,PORT}REVISION variables from release(7), andgjb2013-08-141-19/+4
| | | | | | | | update the default {SRC,DOC,PORT}BRANCH defaults. Submitted by: nwhitehorn X-MFC-With: r254224, r254294 X-MFC-To: stable/9, releng/9.2
* Use kld_{load,unload} instead of mod_{load,unload} for the linker file loadmarkj2013-08-141-4/+4
| | | | | | | and unload event handlers added in r254266. Reported by: jhb X-MFC with: r254266
* - Remove the defaults for TARGET/TARGET_ARCH.gjb2013-08-131-8/+5
| | | | | | | | | - Note that WORLD_FLAGS and KERNEL_FLAGS set the number of make(1) jobs only on SMP-capable systems. MFC after: 3 days X-MFC-With: r254224 X-MFC-To: stable/9, releng/9.2
* Add event handlers for module load and unload events. The load handlers aremarkj2013-08-131-1/+7
| | | | | | | | | called after the module has been loaded, and the unload handlers are called before the module is unloaded. Moreover, the module unload handlers may return an error to prevent the unload from proceeding. Reviewed by: avg MFC after: 2 weeks
* - Update the wrapper script to 'release.sh', as used by the FreeBSDgjb2013-08-111-71/+230
| | | | | | | | | | | | | | | | | | | | | | Release Engineering Team as of 9.2-RELEASE. - Document that a cross-build release is possible by setting the TARGET and TARGET_ARCH variables. - Include an example of using release.sh with and without the optional configuration file. - Document the supported release.sh configuration file variables. - Update the 'cdrom' target output file to disc1.iso. - Update the 'memstick' target output file to memstick.img. - Add attributions for the last major updates to this manual page. - Fix some mdoc(7) style nits: - Sentences should begin on a new line - Use .Pq to enclose full lines in parenthesis
* mdoc: remove commented out macro, sort SEE ALSO and add missing .El.joel2013-08-101-6/+6
|
* Minor mdoc nits.joel2013-08-101-2/+1
|
* mdoc: document title should be all caps.joel2013-08-101-1/+1
|
* * Add random_adaptors.[ch] which is basically a store of random_adaptor's.obrien2013-08-091-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah * Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones. * If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed. * Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one. Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: so (des)
* Give mutex(9) the ability to recurse on a per-instance basis.attilio2013-08-091-2/+10
| | | | | | | | | | Now the MTX_RECURSE flag can be passed to the mtx_*_flag() calls. This helps in cases we want to narrow down to specific calls the possibility to recurse for some locks. Sponsored by: EMC / Isilon storage division Reviewed by: jeff, alc Tested by: pho
* The soft and hard busy mechanism rely on the vm object lock to work.attilio2013-08-097-222/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Make section headings for different quirk types consistent.dwmalone2013-08-061-2/+2
|
* Update ciss(4) with new models of raid controllers from HPsbruno2013-08-061-0/+18
| | | | | | Submitted by: scott.benesh@hp.com MFC after: 2 weeks Sponsored by: Hewlett Packard
* - Reimplement $gif_interfaces as a variant of $cloned_interfaces.hrs2013-08-041-1/+25
| | | | | | | | | | | | | | | | | | Newly-configured systems should use $cloned_interfaces. - Call clone_{up,down}() and ifnet_rename() in rc.d/netif {start,stop}. ifnet_rename() now accepts an interface name list as its argument. - Add rc.d/netif clear. The "clear" subcommand is basically equivalent to "stop" but it does not call clone_down(). - Add "ifname:sticky" keyword into $cloned_interfaces. If :sticky is specified, the interface will not be destroyed in rc.d/netif stop. - Add cloned_interfaces_sticky={YES,NO}. This variable globally sets :sticky keyword above for all interfaces. The default value is NO. When cloned_interfaces_sticky=YES, :nosticky keyword can be used to override it on per interface basis.
* Back out r253779 & r253786.obrien2013-07-311-12/+2
|
* Document net.link.bridge.allow_llz_overlap.hrs2013-07-311-9/+9
|
* Import OpenBSD's rsu(4) WLAN driver.rpaulo2013-07-303-0/+226
| | | | | | | | | | | Support chipsets are the Realtek RTL8188SU, RTL8191SU, and RTL8192SU. Many thanks to Idwer Vollering for porting/writing the man page and for testing. Reviewed by: adrian, hselasky Obtained from: OpenBSD Tested by: kevlo, Idwer Vollering <vidwer at gmail.com>
* Decouple yarrow from random(4) device.obrien2013-07-291-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c comprise yarrow. * random(4) device doesn't really depend on rijndael-*. Yarrow, however, does. * Add random_adaptors.[ch] which is basically a store of random_adaptor's. random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah * Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones. * If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed. * Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one. Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: obrien
* Document the sbinuptime() and getsbinuptime() functions introduced inbrooks2013-07-252-6/+23
| | | | | | r247452. Sponsored by: DARPA, AFRL
* Add TP-LINK TL-WDN4800.pluknet2013-07-221-0/+1
| | | | | PR: docs/180743 Reviewed by: adrian
OpenPOWER on IntegriCloud