| /Documentation/vm/ |
| D | split_page_table_lock.rst | 4 Split page table lock
10 scalability, split page table lock was introduced.
12 With split page table lock we have separate per-table lock to serialize
13 access to the table. At the moment we use split lock for PTE and PMD
16 There are helpers to lock/unlock a table and other accessor functions:
19 maps pte and takes PTE table lock, returns pointer to the taken
22 unlocks and unmaps PTE table;
24 allocates PTE table if needed and take the lock, returns pointer
27 returns pointer to PTE table lock;
29 takes PMD table lock, returns pointer to taken lock;
[all …]
|
| D | mmu_notifier.rst | 3 When do you need to notify inside page table lock ?
8 the page table lock. But that notification is not necessary in all cases.
11 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
13 those secondary TLB while holding page table lock when clearing a pte/pmd:
16 B) a page table entry is updated to point to a new page (COW, write fault
25 - take page table lock
26 - clear page table entry and notify ([pmd/pte]p_huge_clear_flush_notify())
27 - set page table entry to point to new page
29 If clearing the page table entry is not followed by a notify before setting
55 CPU-thread-0 {COW_step1: {update page table to point to new page for addrA}}
[all …]
|
| /Documentation/arm64/ |
| D | acpi_object_usage.rst | 10 the table signature (the first four bytes of the table) is the only portion
11 of the table recognized by the specification, and the actual table is defined
28 Table Usage for ARMv8 Linux
32 **Boot Error Record Table**
35 is recommended this table be supplied.
39 **simple BOOT flag table**
41 Microsoft only table, will not be supported.
45 **Boot Graphics Resource Table**
52 **Corrected Platform Error Polling table**
60 **Core System Resources Table**
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
74 the packet. A ``table`` describes hardware blocks. An ``entry`` describes
75 the actual content of a specific table.
85 is hardware counting for a specific table.
90 * ``table_get``: Receive a table's description.
92 * ``entries_get``: Receive a table's current entries.
93 * ``counters_set``: Enable or disable counters on a table.
95 Table section in Model
98 The driver should implement the following operations for each table:
102 * ``entries_dump``: Dump the actual content of the table.
[all …]
|
| D | mlx5.rst | 13 .. list-table:: Generic parameters implemented
23 .. list-table:: Driver-specific parameters implemented
43 - Control the number of large groups (size > 1) in the FDB table.
54 .. list-table:: devlink info versions implemented
|
| /Documentation/ABI/testing/ |
| D | configfs-acpi | 9 What: /config/acpi/table
15 tables. The attributes of a user define table are:
21 closed the table will be loaded and ACPI devices
28 after the table has been loaded by filling the aml entry:
31 - ASCII table signature
34 - length of table in bytes, including the header
43 - ASCII OEM table identification
|
| D | sysfs-firmware-efi | 5 EFI system table.
11 Description: It shows the physical address of runtime service table entry in
12 the EFI system table.
18 Description: It shows the physical address of config table entry in the EFI
19 system table.
26 Tables found via the EFI System Table. The order in
36 Table version 2 on Dell EMC PowerEdge systems in binary format
|
| D | sysfs-ibft | 5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
22 files that expose the iSCSI Boot Firmware Table NIC data.
30 acpi table header of the iBFT structure. This will allow for
31 identification of the creator of the table which is useful in
|
| D | sysfs-firmware-dmi-tables | 6 data referenced by a SMBIOS table entry point. The SMBIOS
8 version, DMI table size, etc. The structure, content and
15 from /dev/mem. The raw SMBIOS entry point and DMI table are
|
| /Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 27 - ACPI_SIG_FACS (does not have an ordinary ACPI table header)
44 ACPI BIOS table compatibility with the Linux kernel by modifying old
61 # For example add this statement into a _PRT (PCI Routing Table) function
71 # archive. Note that if the table put here matches a platform table
72 # (similar Table Signature, and similar OEMID, and similar OEM Table ID)
73 # with a more recent OEM Revision, the platform table will be upgraded by
74 # this table. If the table put here doesn't match a platform table
75 # (dissimilar Table Signature, or dissimilar OEMID, or dissimilar OEM Table
76 # ID), this table will be appended.
94 [ 1.268089] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.txt | 6 Voltage Table: When in this mode, a voltage table (See below) of
9 only operate at the voltages supplied in the table.
21 voltage-table mode above. This solution does make an
32 Only required for Voltage Table Mode:
33 - voltage-table: Voltage and Duty-Cycle table consisting of 2 cells
49 NB: To be clear, if voltage-table is provided, then the device will be used
50 in Voltage Table Mode. If no voltage-table is provided, then the device will
77 Voltage Table Example:
86 voltage-table = <1114000 0>,
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-emc.txt | 30 Embedded Memory Controller ram-code table
33 next level of nodes below the emc table are used to specify which settings
47 Embedded Memory Controller configuration table
49 This is a table containing the EMC register settings for the various
69 - name : Should be emc-table
70 - compatible : Should contain "nvidia,tegra20-emc-table".
72 the valid frequency for which the table should be used (in kHz).
74 table should be used (in kHz).
86 emc-table@166000 {
88 compatible = "nvidia,tegra20-emc-table";
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 37 a custom configuration table defined by the stub itself. Unfortunately,
38 the events generated by ExitBootServices() don't end up in the table.
40 The firmware provides so called final events configuration table to sort
41 out this issue. Events gets mirrored to this table after the first time
46 final events table size while the stub is still running to the custom
47 configuration table so that the TPM driver can later on skip these events when
48 concatenating two halves of the event log from the custom configuration table
49 and the final events table.
|
| /Documentation/sphinx-static/ |
| D | theme_overrides.css | 56 /* Keep fields from being strangely far apart due to inheirited table CSS. */
57 .rst-content table.field-list th.field-name {
61 .rst-content table.field-list td.field-body {
76 /* table:
83 .wy-table-responsive table td { white-space: normal; }
84 .wy-table-responsive { overflow: auto; }
85 .rst-content table.docutils caption { text-align: left; font-size: 100%; }
98 caption, .wy-table caption, .rst-content table.field-list caption {
|
| /Documentation/filesystems/ |
| D | squashfs.rst | 82 | inode table |
85 | table |
88 | table |
91 | table |
94 | lookup table |
97 | table |
139 in a directory table. Directories are accessed using the start address of
184 3.5 Fragment lookup table
188 location on disk and compressed size using a fragment lookup table. This
189 fragment lookup table is itself stored compressed into metadata blocks.
[all …]
|
| D | files.rst | 8 and file descriptor table (struct files) works.
10 Up until 2.6.12, the file descriptor table has been protected
13 of the table. ->count was used for sharing the file descriptor
14 table between tasks cloned with CLONE_FILES flag. Typically
17 a put_files_struct() frees the file descriptor (fd) table.
23 based on RCU. The file descriptor table contains multiple
28 table are in a separate structure - struct fdtable.
30 which the actual fd table is accessed. Initially the
61 3. For any update to the fd table, files->file_lock must
|
| /Documentation/networking/ |
| D | vrf.rst | 17 through the socket then use the routing table associated with the VRF
31 A VRF device is created with an associated route table. Network interfaces
35 | vrf-blue | ===> route table 10
66 1. VRF device is created with an association to a FIB table.
69 ip link add vrf-blue type vrf table 10
72 2. An l3mdev FIB rule directs lookups to the table associated with the device.
80 ip ru add oif vrf-blue table 10
81 ip ru add iif vrf-blue table 10
83 3. Set the default route for the table (and hence default route for the VRF)::
85 ip route add table 10 unreachable default metric 4278198272
[all …]
|
| D | vxlan.rst | 33 entry in the forwarding table. The destination port number is set to
48 forwarding table using the new bridge command.
50 1. Create forwarding table entry::
54 2. Delete forwarding table entry::
58 3. Show forwarding table::
80 UDP port table 0:
84 UDP port table 1:
|
| /Documentation/security/ |
| D | siphash.rst | 16 sequence numbers, secure cookies, or mask it off for use in a hash table.
59 void init_hashtable(struct some_hashtable *table)
61 get_random_bytes(&table->key, sizeof(table->key));
64 …static inline hlist_head *some_hashtable_bucket(struct some_hashtable *table, struct interesting_i…
66 …return &table->hashtable[siphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtable…
171 void init_hashtable(struct some_hashtable *table)
173 get_random_bytes(&table->key, sizeof(table->key));
176 …static inline hlist_head *some_hashtable_bucket(struct some_hashtable *table, struct interesting_i…
178 …return &table->hashtable[hsiphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtabl…
|
| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 10 the block group descriptor table unless the sparse\_super feature flag
14 the inode table (i.e. they can float). This means that within a block
16 and the group descriptor table. The flex\_bg mechanism uses this
45 .. list-table::
64 - Lower 32-bits of location of inode table.
80 - Block group flags. See the bgflags_ table below.
98 inode table for this group.
124 - Upper 32-bits of location of inodes table.
162 .. list-table::
169 - inode table and bitmap are not initialized (EXT4\_BG\_INODE\_UNINIT).
[all …]
|
| D | bitmaps.rst | 9 The inode bitmap records which entries in the inode table are in use.
12 block or inode table entry. This implies a block group size of 8 \*
23 Inode Table
26 descriptor points to the start of the table, and the superblock records
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 425 with the bad block marker positions. See bad block table support for
428 Bad block table support
435 the first page in the block. This is time consuming so a bad block table
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
452 The bad block table is located at a fixed offset in the chip
457 The bad block table is automatically placed and detected either at
462 The bad block table is mirrored on the chip (device) to allow updates
463 of the bad block table without data loss.
466 nand_default_bbt() selects appropriate default bad block table
[all …]
|
| /Documentation/powerpc/ |
| D | associativity.rst | 59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing
61 used as an index while computing numa distance information via "ibm,numa-distance-table".
67 "ibm,numa-lookup-index-table" = {4, 0, 8, 250, 252}. The offset of domainID 8 (2) is used when
71 "ibm,numa-distance-table" property contains a list of one or more numbers representing the NUMA
77 numa-lookup-index-table.
80 ibm,numa-lookup-index-table = <3 0 8 40>;
81 ibm,numa-distace-table = <9>, /bits/ 8 < 10 20 80 20 10 160 80 160 10>;
102 "ibm,lookup-index-table" helps in having a compact representation of distance matrix.
104 With "ibm,lookup-index-table" we can achieve a compact representation of
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | battery.yaml | 73 resistance-temp-table:
83 for each of the battery capacity lookup table.
110 '^ocv-capacity-table-[0-9]+$':
147 /* table for -10 degree Celsius */
148 ocv-capacity-table-0 = <4185000 100>, <4113000 95>, <4066000 90>;
149 /* table for 0 degree Celsius */
150 ocv-capacity-table-1 = <4200000 100>, <4185000 95>, <4113000 90>;
151 /* table for 10 degree Celsius */
152 ocv-capacity-table-2 = <4250000 100>, <4200000 95>, <4185000 90>;
153 resistance-temp-table = <20 100>, <10 90>, <0 80>, <(-10) 60>;
|
| /Documentation/devicetree/bindings/power/ |
| D | qcom,rpmpd.yaml | 33 opp-table:
46 // Example 1 (rpmh power domain controller and OPP table):
55 rpmhpd_opp_table: opp-table {
102 // Example 2 (rpm power domain controller and OPP table):
109 rpmpd_opp_table: opp-table {
140 // Example 3 (Client/Consumer device using OPP table):
149 leaky_opp_table: opp-table {
|