Searched full:is (Results 1 – 25 of 4308) sorted by relevance
12345678910>>...173
| /Documentation/admin-guide/ |
| D | kernel-parameters.rst | 6 The following is a consolidated list of the kernel parameters as implemented
16 Everything after "``--``" is passed as an argument to init.
46 nohz_full, irqaffinity, rcu_nocbs. The format of this list is:
74 Keep in mind that "N" is dynamic, so if system changes cause the bitmap width
80 so that "nohz_full=all" is the equivalent of "nohz_full=0-N".
82 The semantics of "N" and "all" is supported on a level of bitmaps and holds for
93 were enabled and if respective hardware is present. This list should be kept
96 is applicable::
98 ACPI ACPI support is enabled.
99 AGP AGP (Accelerated Graphics Port) is enabled.
[all …]
|
| D | thunderbolt.rst | 6 USB4 is the public specification based on Thunderbolt 3 protocol with
8 manager is an entity running on the host router (host controller)
17 connection manager implementation is to be used. To be on the safe side the
19 ``user`` which means PCIe tunneling is disabled by default. The
22 is expected to be accompanied with an IOMMU based DMA protection.
26 The interface presented here is not meant for end users. Instead there
45 (usbonly). The reason for these is the fact that the connected devices can
48 it is not always available for various reasons.
50 Some USB4 systems have a BIOS setting to disable PCIe tunneling. This is
57 approval is needed. In BIOS settings this is typically called
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 10 debugobjects is a generic infrastructure to track the life time of
13 debugobjects is useful to check for the following error patterns:
21 debugobjects is not changing the data structure of the real object so it
56 Each detected error is reported in the statistics and a limited number
70 This function is called whenever the initialization function of a real
71 object is called.
73 When the real object is already tracked by debugobjects it is checked,
74 whether the object can be initialized. Initializing is not allowed for
82 When the real object is not yet tracked by debugobjects, debugobjects
84 object state to ODEBUG_STATE_INIT. It verifies that the object is not
[all …]
|
| D | swiotlb.rst | 7 swiotlb is a memory buffer allocator used by the Linux kernel DMA layer. It is
11 to the limitations. The DMA is done to/from this temporary memory buffer, and
13 memory buffer. This approach is generically called "bounce buffering", and the
14 temporary memory buffer is called a "bounce buffer".
20 if bounce buffering is necessary. If so, the DMA layer manages the allocation,
25 memory buffer, doing bounce buffering is slower than doing DMA directly to the
26 original memory buffer, and it consumes more CPU resources. So it is used only
38 encrypted by default, and the memory is not accessible by the host hypervisor
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
41 to force all DMA I/O to use bounce buffers, and the bounce buffer memory is set
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 5 Driver binding is the process of associating a device with a device
16 type in the system. When device_register is called for a device, it is
18 list of all drivers of that bus type. When driver_register is called
19 for a driver, it is inserted at the end of this list. These are the
26 When a new device is added, the bus's list of drivers is iterated over
29 supports. The format and semantics for comparing IDs is bus-specific.
31 algorithm, it is up to the bus driver to provide a callback to compare
37 If a match is found, the device's driver field is set to the driver
38 and the driver's probe callback is called. This gives the driver a
45 Upon the successful completion of probe, the device is registered with
[all …]
|
| /Documentation/networking/ |
| D | ipvs-sysctl.rst | 13 It sets the always mode drop rate, which is used in the mode 3
19 It sets the available memory threshold (in pages), which is
20 used in the automatic modes of defense. When there is no
22 enabled and the variable is automatically set to 2, otherwise
23 the strategy is disabled and the variable is set to 1.
29 If set, disable the director function while the server is
36 port reuse. It is a bitmap, with the values being:
42 bit 1: enable rescheduling of new connections when it is safe.
43 That is, whenever expire_nodest_conn and for TCP sockets, when
44 the connection is in TIME_WAIT state (which is only possible if
[all …]
|
| D | strparser.rst | 10 The stream parser (strparser) is a utility that parses messages of an
20 In receive callback mode, the strparser is called from the data_ready
25 outside source. Message are parsed and delivered as the sequence is
34 callbacks include a parse_msg function that is called to perform
36 that is called when a full message has been completed.
46 Called to initialize a stream parser. strp is a struct of type
47 strparser that is allocated by the upper layer. sk is the TCP
49 callback mode; in general mode this is set to NULL. Callbacks
56 Temporarily pause a stream parser. Message parsing is suspended
69 strp_stop is called to completely stop stream parser operations.
[all …]
|
| /Documentation/scsi/ |
| D | st.rst | 8 The driver is currently maintained by Kai Mäkisara (email
17 The driver is generic, i.e., it does not contain any code tailored
22 directly with ioctls. This is administratively a very simple and
30 new tape is loaded into the drive or if writing begins at the
31 beginning of the tape. The second method is applicable if the tape
33 QIC-drives). The result is that any tape can be read, writing can be
34 continued using existing format, and the default format is used if
35 the tape is rewritten from the beginning (or a new tape is written
36 for the first time). The first method is applicable if the drive
37 does not perform auto-detection well enough and there is a single
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 5 Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
6 addressed by PPL is that after a dirty shutdown, parity of a particular stripe
7 may become inconsistent with data on other member disks. If the array is also
8 in degraded state, there is no way to recalculate parity, because one of the
9 disks is missing. This can lead to silent data corruption when rebuilding the
10 array or using it is as degraded - data calculated from parity for array blocks
12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
15 Partial parity for a write operation is the XOR of stripe data chunks not
16 modified by this write. It is just enough data needed for recovering from the
20 this stripe is missing, this updated parity can be used to recover its
[all …]
|
| /Documentation/arch/x86/ |
| D | mds.rst | 9 Microarchitectural Data Sampling (MDS) is a family of side channel attacks
21 buffers are partitioned between Hyper-Threads so cross thread forwarding is
23 buffer is repartitioned which can expose data from one thread to the other.
26 L1 miss situations and to hold data which is returned or sent in response
28 operation and also write data to the cache. When the fill buffer is
32 Hyper-Threads so cross thread leakage is possible.
35 from memory or I/O. The received data is then forwarded to the register
40 thread leakage is possible.
42 MDSUM is a special case of MSBDS, MFBDS and MLPDS. An uncacheable load from
50 It is assumed that attack code resides in user space or in a guest with one
[all …]
|
| /Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 11 are to be used. If no huge page exists at page fault time, the task is sent
14 of huge pages at mmap() time. The idea is that if there were not enough
21 describe how huge page reserve processing is done in the v4.10 kernel.
26 This description is primarily targeted at kernel developers who are modifying
34 This is a global (per-hstate) count of reserved huge pages. Reserved
36 Therefore, the number of huge pages generally available is computed
39 A reserve map is described by the structure::
50 There is one reserve map for each huge page mapping in the system.
52 the mapping. A region is described as::
68 Indicates this task is the owner of the reservations
[all …]
|
| /Documentation/locking/ |
| D | rt-mutex-design.rst | 13 that happen without this code, but that is in the concept to understand
14 what the code actually is doing.
16 The goal of this document is to help others understand the priority
17 inheritance (PI) algorithm that is used, as well as reasons for the
24 Priority inversion is when a lower priority process executes while a higher
28 the high priority process must wait until the lower priority process is done
29 with the resource. This is a priority inversion. What we want to prevent
30 is something called unbounded priority inversion. That is when the high
31 priority process is prevented from running by a lower priority process for
34 The classic example of unbounded priority inversion is where you have three
[all …]
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 11 This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
21 to test this driver may be found there as well. Support is also available from
27 this driver was tested against. The sopc2dts tool is used to create the
31 Triple-Speed Ethernet instance is using an SGDMA or MSGDMA component. The
36 The SGDMA component is to be deprecated in the near future (over the next 1-2
38 SGDMA support is included for existing designs and reference in case a
46 Scatter-gather DMA is not supported by the SGDMA or MSGDMA at this time.
58 The kernel configuration option is ALTERA_TSE:
67 - dma_rx_num: Number of descriptors in the RX list (default is 64);
68 - dma_tx_num: Number of descriptors in the TX list (default is 64).
[all …]
|
| /Documentation/filesystems/ |
| D | autofs.rst | 8 The goal of autofs is to provide on-demand mounting and race free
12 1. There is no need to delay boot until all filesystems that
15 continue freely. This is particularly important for
30 The "autofs" filesystem module is only one part of an autofs system.
38 "autofs" is a Linux kernel module which provides the "autofs"
52 directory should be a mount trap is based on a master map. This master
53 map is consulted by autofs to determine which directories are mount
55 On most systems, the default master map is located at */etc/auto.master*.
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
[all …]
|
| D | path-lookup.rst | 5 This write-up is based on three articles published at lwn.net:
22 exploration is needed to discover, is that it is complex. There are
26 tool that we will make extensive use of is "divide and conquer". For
51 It is tempting to describe the second kind as starting with a
53 slashes and components, it can be empty, in other words. This is
55 in Linux permit it when the ``AT_EMPTY_PATH`` flag is given. For
61 everything else. The "everything else" is the easy bit. In all cases
65 The final component is not so simple. Not only do different system
68 pathname that is just slashes have a final component. If it does
85 directory entry that is to be created for a directory immediately
[all …]
|
| D | sharedsubtree.rst | 45 Here is an example:
47 Let's say /mnt has a mount that is shared::
52 so the sample 'smount' program is no longer needed and has been
82 And the same is true even when /dev/sd0 is mounted on /mnt/a. The
86 2b) A slave mount is like a shared mount except that mount and umount events
89 All slave mounts have a master mount which is a shared.
91 Here is an example:
93 Let's say /mnt has a mount which is shared.
99 the new mount at /tmp becomes a shared mount and it is a replica of
131 This is the mount we are familiar with. Its the default type.
[all …]
|
| /Documentation/block/ |
| D | ublk.rst | 10 ublk is a generic framework for implementing block device logic from userspace.
11 The motivation behind it is that moving virtual block drivers into userspace,
28 ublk block device (``/dev/ublkb*``) is added by ublk driver. Any IO request
31 program. ``ublksrv`` [#userspace]_ is one of such implementation. It
33 user block device conveniently, while also generic type block device is
37 After the IO is handled by userspace, the result is committed back to the
39 logic is totally done by userspace, such as loop's IO handling, NBD's IO
42 ``/dev/ublkb*`` is driven by blk-mq request-based driver. Each request is
44 IO too, which is 1:1 mapped with IO of ``/dev/ublkb*``.
47 ``io_uring`` passthrough command; that is why ublk is also one io_uring based
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 45 When this property is omitted, it is assumed that the device is using what
46 the datasheet calls "4-wire mode". This is the conventional SPI mode used
48 line is used to initiate the conversion and the SDI line is connected to
51 When this property is present, it indicates that the device is using one
55 definition of 3-wire mode is NOT at all related to the standard
56 spi-3wire property!) This mode is often used when the ADC is the only
57 device on the bus. In this mode, SDI is tied to VIO, and the CNV line
59 which case the CS line of the controller is unused.
60 * chain: The datasheet calls this "chain mode". This mode is used to save
62 one chip is tied to the SDO of the next chip in the chain and the SDI of
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-g-mode.rst | 41 depending on the chosen mode. The initiator is the filehandle that is
43 follower is the filehandle that receives messages sent to the CEC
47 When a CEC message is received, then the CEC framework will decide how
48 it will be processed. If the message is a reply to an earlier
49 transmitted message, then the reply is sent back to the filehandle that
50 is waiting for it. In addition the CEC framework will process it.
52 If the message is not a reply, then the CEC framework will process it
53 first. If there is no follower, then the message is just discarded and a
54 feature abort is sent back to the initiator if the framework couldn't
55 process it. If there is a follower, then the message is passed on to the
[all …]
|
| D | cec-ioc-receive.rst | 42 If the file descriptor is in non-blocking mode and there are no received
44 error code. If the file descriptor is in blocking mode and ``timeout``
45 is non-zero and no message arrived within ``timeout`` milliseconds, then
60 The :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` is only available if
61 ``CEC_CAP_TRANSMIT`` is set. If there is no more room in the transmit
65 to core messages (see :ref:`cec-core-processing`), so it is not a good
68 If the file descriptor is in non-blocking mode then the transmit will
77 address is invalid (due to e.g. a disconnect) will return ``ENONET``.
80 'TV' when the physical address is invalid since some TVs pull the hotplug detect
85 physical address, but the cable is still connected and CEC still works.
[all …]
|
| /Documentation/arch/riscv/ |
| D | hwprobe.rst | 6 The RISC-V hardware probing interface is based around a single syscall, which
7 is defined in <asm/hwprobe.h>::
21 value if the key is recognized. If a key is unknown to the kernel, its key field
22 will be cleared to -1, and its value set to 0. The CPU set is defined by
32 set of CPUs, the values of each key are given and the set of CPUs is reduced
34 How matching is done depends on the key type. For value-like keys, matching
36 means the result of a logical AND of the pair's value with the CPU's value is
37 exactly the same as the pair's value. Additionally, when ``cpus`` is an empty
38 set, then it is initialized to all online CPUs which fit within it, i.e. the
39 CPU set returned is the reduction of all the online CPUs which can be
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 17 The "security" sysfs attribute is provided in the nvdimm sysfs directory. For
23 frozen, and overwrite. If security is not supported, the sysfs attribute
26 The "store" attribute takes several commands when it is being written to
39 The key is associated to the payload by the DIMM id. For example:
46 key "passphrase" is expected to be 32bytes long. This is similar to the ATA
47 security specification [2]. A key is initially acquired via the request_key()
48 kernel API call during nvdimm unlock. It is up to the user to make sure that
55 encrypted-keys of enc32 format. TPM usage with a master trusted key is
61 retrieve the key from the kernel user keyring. This is the only time
66 the passphrase for the respective nvdimms. It is also recommended that the
[all …]
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 10 rmnet driver is used for supporting the Multiplexing and aggregation
11 Protocol (MAP). This protocol is used by all recent chipsets using Qualcomm
23 Aggregation is required to achieve high data rates. This involves hardware
42 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
43 or data packet. Command packet is used for transport level flow control. Data
48 Padding is the number of bytes to be appended to the payload to
51 Multiplexer ID is to indicate the PDN on which data has to be sent.
68 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
69 or data packet. Command packet is used for transport level flow control. Data
74 Padding is the number of bytes to be appended to the payload to
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 14 device driver in the Linux kernel tree. The spidernet is a gigabit
20 The receive (RX) ring is a circular linked list of RX descriptors,
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
32 descriptor is neither empty or full; it is simply not ready. It may
33 not even have a data buffer in it, or is otherwise unusable.
38 ring is handed off to the hardware, which sequentially fills in the
42 This filling and emptying is managed by three pointers, the "head"
45 currently being filled. When this descr is filled, the hardware
46 marks it full, and advances the GDACTDPA by one. Thus, when there is
[all …]
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 16 and the earliest posted-receive is the pair that must be used to satisfy the
21 When a message is sent from the sender to the receiver, the communication
23 corresponding matching receive is posted. If a matching receive is posted,
24 this is an expected message, otherwise it is called an unexpected message.
31 1. The Eager protocol- the complete message is sent when the send is
32 processed by the sender. A completion send is received in the send_cq
37 corresponding buffer is posted, the responder will use the information from
50 When send is initiated and arrives at the receive side, if there is no
51 pre-posted receive for this arriving message, it is passed to the software and
52 placed in the unexpected message list. Otherwise the match is processed,
[all …]
|
12345678910>>...173