| /freebsd-13-stable/usr.sbin/iostat/ |
| HD | iostat.8 | 129 will show devices in order from highest to lowest bytes
150 number of devices.
153 utility will display fewer devices if there are less than
155 devices present.
174 Specify which types of devices to display.
175 There are three different categories of devices:
181 Direct Access devices
183 Sequential Access devices
187 Processor devices
189 Write Once Read Multiple devices
[all …]
|
| /freebsd-13-stable/lib/libdevstat/ |
| HD | devstat.3 | 64 .Fa "struct devstat *devices"
123 returns the number of devices registered with the
132 list of devices in the kernel.
157 fetches the current list of devices and statistics into the supplied
193 struct devstat *devices;
215 variable (which is available for convenience), the list of devices could
226 The devices subelement of the
242 number of devices registered with the kernel
249 selects devices to display based upon a number of criteria:
251 .It specified devices
[all …]
|
| HD | devstat.c | 178 * Find out how many devices we have in the system. in devstat_getnumdevs()
184 "%s: error getting number of devices\n" in devstat_getnumdevs()
324 * Get the current list of devices and statistics, and the current
359 * Get the number of devices. If it's negative, it's an in devstat_getdevs()
368 * generation number, as well as all the devices. in devstat_getdevs()
385 * Request all of the devices. We only really allow for one in devstat_getdevs()
389 * If devices are being added to the system that quickly, maybe in devstat_getdevs()
390 * the user can just wait until all devices are added. in devstat_getdevs()
402 * more devices now, so we need to allocate more in devstat_getdevs()
458 * devices is not the same as the number of devices recorded in the in devstat_getdevs()
[all …]
|
| /freebsd-13-stable/sys/contrib/openzfs/man/man7/ |
| HD | zpoolconcepts.7 | 38 .Ss Virtual Devices (vdevs)
39 A "virtual device" describes a single device or a collection of devices
41 The following virtual devices are supported:
65 A mirror of two or more devices.
69 devices failing without losing data.
94 .Em (N-P)*X No bytes and can withstand Em P No devices failing without losing data.
95 The minimum number of devices in a raidz group is one more than the number of
102 .Em D No data devices and Em P No parity devices.
142 devices failing without losing data.
152 The number of data devices per redundancy group.
[all …]
|
| /freebsd-13-stable/usr.bin/vmstat/ |
| HD | vmstat.8 | 135 Specify which types of devices to display.
137 categories of devices:
143 Direct Access devices
145 Sequential Access devices
149 Processor devices
151 Write Once Read Multiple devices
153 CD devices
155 Scanner devices
157 Optical Memory devices
159 Medium Changer devices
[all …]
|
| /freebsd-13-stable/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/io/ |
| HD | tst.fds.d.out | 2 fds[0] fi_dirname = /devices/pseudo
3 fds[0] fi_pathname = /devices/pseudo/mm@0:null
5 fds[0] fi_mount = /devices
9 fds[1] fi_dirname = /devices/pseudo
10 fds[1] fi_pathname = /devices/pseudo/mm@0:null
12 fds[1] fi_mount = /devices
16 fds[2] fi_dirname = /devices/pseudo
17 fds[2] fi_pathname = /devices/pseudo/mm@0:null
19 fds[2] fi_mount = /devices
23 fds[3] fi_dirname = /devices/pseudo
[all …]
|
| /freebsd-13-stable/sys/contrib/openzfs/man/man8/ |
| HD | zpool-initialize.8 | 46 devices, or all eligible devices in the pool if no individual devices are
48 Only leaf data or log devices may be initialized.
51 Cancel initializing on the specified devices, or all eligible devices if none
53 If one or more target devices are invalid or are not currently being
56 Suspend initializing on the specified devices, or all eligible devices if none
58 If one or more target devices are invalid or are not currently being
62 with no flags on the relevant target devices.
64 Clears the initialization state on the specified devices, or all eligible
65 devices if none are specified.
66 If the devices are being actively initialized the command will fail.
[all …]
|
| HD | zpool-trim.8 | 48 This operation informs the underlying storage devices of all blocks
50 devices to reclaim the space.
57 property above for the types of vdev devices which can be trimmed.
72 Cancel trimming on the specified devices, or all eligible devices if none
74 If one or more target devices are invalid or are not currently being
77 Suspend trimming on the specified devices, or all eligible devices if none
79 If one or more target devices are invalid or are not currently being
83 with no flags on the relevant target devices.
85 Wait until the devices are done being trimmed before returning.
|
| /freebsd-13-stable/crypto/openssh/ |
| HD | auth2-chall.c | 64 KbdintDevice *devices[] = { variable
78 char *devices; member
91 for (i = 0; devices[i] != NULL; i++) in remove_kbdint_device()
92 if (strcmp(devices[i]->name, devname) == 0) { in remove_kbdint_device()
93 for (j = i; devices[j] != NULL; j++) in remove_kbdint_device()
94 devices[j] = devices[j+1]; in remove_kbdint_device()
116 for (i = 0; devices[i]; i++) { in kbdint_alloc()
118 sshbuf_len(b) ? "," : "", devices[i]->name)) != 0) in kbdint_alloc()
121 if ((kbdintctxt->devices = sshbuf_dup_string(b)) == NULL) in kbdint_alloc()
125 kbdintctxt->devices = xstrdup(devs); in kbdint_alloc()
[all …]
|
| /freebsd-13-stable/share/man/man4/ |
| HD | intro.4 | 32 .Nd introduction to devices and device drivers
34 This section contains information related to devices, device drivers
41 .Em pseudo-devices
53 The set of system calls available for devices is chosen from
72 .Ss Accessing Devices
73 Most of the devices in
91 For pseudo-devices, device nodes may be created and removed dynamically
106 of devices visible within different instances of the
109 subsystems from accessing unsafe devices.
113 Drivers for network devices do not use device nodes in order to be
[all …]
|
| HD | scsi.4 | 60 devices, and to utilize different
67 When the system probes buses, it attaches any devices it finds to the
71 driver, if it is configured in the kernel, will attach to all devices.
79 for discovery of additional devices which may take time to connect,
83 performance of the storage devices.
85 Enable collection of statistics for periph devices.
149 devices need some amount of time to recover from a bus reset.
151 may need as little as 100ms, while old, slow devices may need much longer.
166 All devices and buses support dynamic allocation so that
167 an upper number of devices and controllers does not need to be configured;
[all …]
|
| HD | uart.4 | 31 .Nd driver for Universal Asynchronous Receiver/Transmitter (UART) devices
75 The primary support for devices that contain multiple serial interfaces or
82 However, the serial interfaces of those devices that are managed by the
118 .Ss SYSTEM DEVICES
119 System devices are UARTs that have a special purpose by way of hardware
134 System devices, with the notable exception of serial consoles, generally
168 tunable configures the PPS capture mode for all uart devices;
226 .Sh Special Devices
230 device for each of the callin and the callout "data" devices.
236 in the normal way on the initial-state devices to program
[all …]
|
| HD | pci.4 | 56 devices in the kernel and limited access to
58 devices for userland.
69 devices, or all
71 devices that match various patterns.
98 It enumerates any devices on the
135 devices in the system, or on
137 devices matching patterns supplied by the user.
199 Buffer containing matching devices returned by the kernel.
266 This means that there are no more devices in the PCI device list matching
283 remaining devices in the device list that match his criteria.
[all …]
|
| HD | superio.4 | 48 Super I/O is an I/O controller that combines various low-bandwidth devices
50 A typical Super I/O can contain devices such as
70 driver provides support for devices residing in the Super I/O controller
72 Some of the Super I/O devices have standardized interfaces.
73 Such devices either use well-known legacy resources or they are advertised
79 driver is not designed to interact with that kind of devices.
86 There are other Super I/O devices that do not have any standardized interface.
87 Drivers for those devices can be written using facilities of the
97 controllers and a bus driver for supported devices in those controllers.
|
| /freebsd-13-stable/contrib/libpcap/doc/ |
| HD | README.macos | 2 the BPF devices to capture packets with libpcap and allows users with
3 write access to the BPF devices to send packets with libpcap.
5 On some systems that use BPF, the BPF devices live on the root file
6 system, and the permissions and/or ownership on those devices can be
8 devices.
10 On newer versions of FreeBSD, the BPF devices live on devfs, and devfs
12 devices to give users other than root permission to read or write those
13 devices.
15 On macOS, the BPF devices live on devfs, but the macOS version of devfs
18 those devices.
[all …]
|
| /freebsd-13-stable/sbin/swapon/ |
| HD | swapon.8 | 35 .Nd "specify devices for paging and swapping"
57 utilities are used to control swap devices in the system.
61 Swap devices use a fixed interleave; the maximum number of devices
67 utility adds the specified swap devices to the system.
70 option is used, all swap devices in
80 swap devices with the
90 option causes each of following devices to receive a
106 utility removes the specified swap devices from the system.
109 option is used, all swap devices in
117 only swap devices with the
[all …]
|
| /freebsd-13-stable/share/doc/papers/devfs/ |
| HD | paper.me | 26 .b "Rethinking /dev and devices in the UNIX kernel"
41 implementation of the ``devices as files'' concept, an implementation which
43 Starting from a high-level view of devices and the semantics that
57 I/O devices in an operating system:
60 The usual way is to treat I/O devices as their own class of things,
62 to the semantics of the devices.
85 There is a threefold advantage in treating I/O devices this way:
182 devices into their computers.
183 These devices can be anything from modems and disks to GPS receivers
186 correct set of special devices in ``/dev'' became a major headache.
[all …]
|
| /freebsd-13-stable/tests/sys/cddl/zfs/tests/devices/ |
| HD | devices_test.sh | 30 …atf_set "descr" "Setting devices=on on file system, the devices files in this filesystem can be us…
35 atf_expect_fail "The devices property is not yet supported on FreeBSD"
38 . $(atf_get_srcdir)/devices.cfg
48 . $(atf_get_srcdir)/devices.cfg
57 …atf_set "descr" "Setting devices=off on file system, the devices files in this filesystem can not …
62 atf_expect_fail "The devices property is not yet supported on FreeBSD"
65 . $(atf_get_srcdir)/devices.cfg
75 . $(atf_get_srcdir)/devices.cfg
90 . $(atf_get_srcdir)/devices.cfg
98 . $(atf_get_srcdir)/devices.cfg
|
| /freebsd-13-stable/contrib/ofed/libibverbs/man/ |
| HD | ibv_get_device_list.3 | 6 ibv_get_device_list, ibv_free_device_list \- get and release list of available RDMA devices
17 returns a NULL-terminated array of RDMA devices currently available.
20 is optional; if not NULL, it is set to the number of devices returned in the array.
23 frees the array of devices
29 returns the array of available RDMA devices, or sets
31 and returns NULL if the request fails. If no devices are found then
48 Client code should open all the devices it intends to use with
53 it will be able to use only the open devices; pointers to unopened devices will no longer be valid.
|
| /freebsd-13-stable/sys/contrib/device-tree/Bindings/timer/ |
| D | ti,timer.txt | 5 OMAP44xx devices have timer instances that are 100%
6 register compatible with OMAP3xxx devices as well as
8 So for OMAP44xx devices timer instances may use
11 ti,omap2420-timer (applicable to OMAP24xx devices)
12 ti,omap3430-timer (applicable to OMAP3xxx/44xx devices)
13 ti,omap4430-timer (applicable to OMAP44xx devices)
14 ti,omap5430-timer (applicable to OMAP543x devices)
15 ti,am335x-timer (applicable to AM335x devices)
16 ti,am335x-timer-1ms (applicable to AM335x devices)
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/devices/ |
| HD | devices_001_pos.ksh | 33 . $STF_SUITE/tests/functional/devices/devices.cfg
34 . $STF_SUITE/tests/functional/devices/devices_common.kshlib
38 # When set property devices=on on file system, devices files can be used in
43 # 2. Set devices=on on this file system.
51 log_assert "Setting devices=on on file system, the devices files in this file" \
55 log_must zfs set devices=on $TESTPOOL/$TESTFS
72 log_pass "Setting devices=on on file system and testing it pass."
|
| HD | devices_002_neg.ksh | 33 . $STF_SUITE/tests/functional/devices/devices.cfg
34 . $STF_SUITE/tests/functional/devices/devices_common.kshlib
38 # When set property devices=off on file system, device files cannot be used
43 # 2. Set devices=off on this file system.
51 log_assert "Setting devices=off on file system, the devices files in this file"\
55 log_must zfs set devices=off $TESTPOOL/$TESTFS
70 log_pass "Setting devices=off on file system and testing it pass."
|
| /freebsd-13-stable/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_import/ |
| HD | import_devices_missing.ksh | 22 # A pool should be importable when up to 2 top-level devices are missing.
27 # 3. Add one or more devices.
30 # 6. Move added devices out of the devices directory.
31 # 7. Import the pool with missing devices.
34 # 10. Export the pool, move back missing devices, Re-import the pool.
77 # Missing devices means that data or metadata may be corrupted.
116 # Note that we are testing for 2 non-consecutive missing devices.
117 # Missing consecutive devices results in missing metadata. Because of
122 log_pass "zpool import succeeded with missing devices."
|
| /freebsd-13-stable/sys/contrib/device-tree/Bindings/ |
| HD | xilinx.txt | 3 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
4 in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range
6 devices (gpio, LCD, spi, etc). Also, since these devices are
25 [, (list of compatible devices), ...];
90 device tree. The following are bindings for specific devices:
116 Xilinx Ethernet devices. In addition to general xilinx properties
117 listed above, nodes for these devices should include a phy-handle
123 Xilinx uartlite devices are simple fixed speed serial ports.
130 Xilinx hwicap devices provide access to the configuration logic
146 Xilinx UART 16550 devices are very similar to the NS16550 but with
[all …]
|
| /freebsd-13-stable/sys/dev/superio/ |
| HD | superio.c | 290 const struct sio_device *devices; member
294 .devices = ite_devices,
298 .devices = ite_devices,
302 .devices = ite_devices,
306 .devices = ite_devices,
310 .devices = ite_devices,
314 .devices = ite_devices,
318 .devices = ite_devices,
322 .devices = ite_devices,
327 .devices = nct5104_devices,
[all …]
|