| /kernel/linux/linux-5.10/Documentation/userspace-api/ |
| D | unshare.rst | 34 requiring additional data structures and mechanisms in the kernel. The
188 appropriate process context structures, populates it with values from
189 the current shared version, associates newly duplicated structures
197 before associating newly duplicated context structures
199 2) unshare() has to allocate and duplicate all context structures
201 current task and releasing older shared structures. Failure
214 appropriate context structures and then associate them with the
225 are new context structures then lock the current task structure,
226 associate new context structures with the current task structure,
229 4) Appropriately release older, shared, context structures.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/userspace-api/ |
| D | unshare.rst | 34 requiring additional data structures and mechanisms in the kernel. The
188 appropriate process context structures, populates it with values from
189 the current shared version, associates newly duplicated structures
197 before associating newly duplicated context structures
199 2) unshare() has to allocate and duplicate all context structures
201 current task and releasing older shared structures. Failure
214 appropriate context structures and then associate them with the
225 are new context structures then lock the current task structure,
226 associate new context structures with the current task structure,
229 4) Appropriately release older, shared, context structures.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 2 A Tour Through TREE_RCU's Data Structures [LWN.net]
12 This document describes RCU's major data structures and their relationship
19 data structures maintain the state in such a way as to allow RCU readers
28 of ``rcu_node`` structures. Each leaf node of the ``rcu_node`` tree has up
29 to 16 ``rcu_data`` structures associated with it, so that there are
30 ``NR_CPUS`` number of ``rcu_data`` structures, one for each possible CPU.
42 Quiescent states are recorded by the per-CPU ``rcu_data`` structures,
44 structures.
66 | ``rcu_node`` structures than further up the tree. Therefore, if the |
67 | leaf ``rcu_node`` structures have fanout of 64, the contention on |
[all …]
|
| /kernel/linux/linux-4.19/Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.html | 4 <head><title>A Tour Through TREE_RCU's Data Structures [LWN.net]</title>
12 This document describes RCU's major data structures and their relationship
39 data structures maintain the state in such a way as to allow RCU readers
48 containing a tree of <tt>rcu_node</tt> structures.
50 <tt>rcu_data</tt> structures associated with it, so that there
51 are <tt>NR_CPUS</tt> number of <tt>rcu_data</tt> structures,
65 Quiescent states are recorded by the per-CPU <tt>rcu_data</tt> structures,
67 structures.
90 <tt>rcu_node</tt> structures than further up the tree.
91 Therefore, if the leaf <tt>rcu_node</tt> structures have fanout of
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | ioctl.rst | 55 Some subsystems use version numbers in data structures to overload
89 incompatible definitions of these structures in user space after the
93 in other data structures when separate second/nanosecond values are
119 As long as all the rules for data structures are followed, this is as
141 are pointers to compatible data structures.
146 Compatible data structures have the same layout on all architectures,
151 data structures. Fixed-length replacements are ``__s32``, ``__u32``,
174 To avoid this problem, all structures should have their members
179 * On ARM OABI user space, structures are padded to multiples of 32-bit,
203 implicit padding in data structures. Where there is implicit padding
|
| D | generic-counter.rst | 244 provides several core data structures, function prototypes, and macros
257 Counter Signals via counter_signal structures. These Signals should
262 Counter Counts may be allocated via counter_count structures, and
264 counter_synapse structures. Associated counter_synapse structures are
266 respective counter_count structure. These counter_count structures are
284 and counter_signal_ext structures. In these cases, the
287 counter_count_ext and counter_signal_ext structures allow for auxiliary
364 structures that are passed in.
|
| /kernel/linux/linux-5.10/fs/xfs/libxfs/ |
| D | xfs_da_format.h | 45 * ignore the differences in the rest of the structures.
105 * Note: many node blocks structures and constants are shared with the attr
117 * is in the block header and dirent formats. In many cases the v3 structures
136 * offsets of all the structures inside the blocks are different.
198 * structures. Due the different inode number storage size and the variable
248 * Data block structures.
263 * As all the entries are variable size structures the accessors below should
267 * most structures are also used for the combined data/freespace "block"
307 * directory block structures. This will be used in several structures.
309 * structures so we determine how to decode them just by the magic number.
[all …]
|
| /kernel/linux/linux-4.19/fs/xfs/libxfs/ |
| D | xfs_da_format.h | 45 * ignore the differences in the rest of the structures.
118 * Note: many node blocks structures and constants are shared with the attr
130 * is in the block header and dirent formats. In many cases the v3 structures
149 * offsets of all the structures inside the blocks are different.
211 * structures. Due the different inode number storage size and the variable
261 * Data block structures.
276 * As all the entries are variable size structures the accessors below should
280 * most structures are also used for the combined data/freespace "block"
320 * directory block structures. This will be used in several structures.
322 * structures so we determine how to decode them just by the magic number.
[all …]
|
| /kernel/linux/linux-4.19/arch/ia64/include/asm/sn/ |
| D | klconfig.h | 15 * The KLCONFIG structures store info about the various BOARDs found
40 * There are 2 different structures to represent these boards -
41 * lboard - Local board, rboard - remote board. These 2 structures
108 * Like BOARD structures, REMOTE ERRINFO structures can be built locally
113 * manipulating the structures, is that, the NODE number information should
118 * Note that these structures do not provide much info about connectivity.
123 * The data structures below define the above concepts.
175 * board structures
|
| D | nodepda.h | 18 * NUMA Node-Specific Data structures are defined in this file.
26 * One of these structures is allocated on each node of a NUMA system.
29 * all per-node data structures.
|
| /kernel/linux/linux-4.19/scripts/gcc-plugins/ |
| D | Kconfig | 76 This plugin zero-initializes any structures containing a
103 bool "Randomize layout of sensitive kernel structures"
106 If you say Y here, the layouts of structures that are entirely
108 __no_randomize_layout), or structures that have been explicitly
139 in structures. This reduces the performance hit of RANDSTRUCT
|
| /kernel/linux/linux-5.10/scripts/gcc-plugins/ |
| D | Kconfig | 64 bool "Randomize layout of sensitive kernel structures"
67 If you say Y here, the layouts of structures that are entirely
69 __no_randomize_layout), or structures that have been explicitly
100 in structures. This reduces the performance hit of RANDSTRUCT
|
| /kernel/linux/linux-4.19/Documentation/device-mapper/ |
| D | persistent-data.txt | 6 different targets were rolling their own data structures, for example:
13 Maintaining these data structures takes a lot of work, so if possible
58 On-disk data structures that keep track of reference counts of blocks.
65 The data structures
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 10 different targets were rolling their own data structures, for example:
17 Maintaining these data structures takes a lot of work, so if possible
62 On-disk data structures that keep track of reference counts of blocks.
69 The data structures
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | pixfmt-v4l2-mplane.rst | 4 Multi-planar format structures
7 The struct :c:type:`v4l2_plane_pix_format` structures define size
11 array of struct :c:type:`v4l2_plane_pix_format` structures,
68 - An array of structures describing format of each plane this pixel
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | boot-time-mm.rst | 7 allocate memory for various data structures, for instance for the
30 Functions and structures
33 Here is the description of memblock data structures, functions and
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-v4l2-mplane.rst | 4 Multi-planar format structures
7 The struct :c:type:`v4l2_plane_pix_format` structures define size
11 array of struct :c:type:`v4l2_plane_pix_format` structures,
86 - An array of structures describing format of each plane this pixel
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_ondisk.h | 25 /* ag/file structures */ in xfs_check_ondisk_structs()
118 /* log structures */ in xfs_check_ondisk_structs()
137 * The v5 superblock format extended several v4 header structures with in xfs_check_ondisk_structs()
139 * superblocks, it's important that the v5 structures place original v4 in xfs_check_ondisk_structs()
144 * The following checks ensure that various v5 data structures place the in xfs_check_ondisk_structs()
|
| /kernel/linux/linux-4.19/Documentation/security/ |
| D | IMA-templates.rst | 25 definition of two new data structures: a template descriptor, to determine
29 Managing templates with these structures is very simple. To support
36 by translating the format into an array of template fields structures taken
53 method for each item of the array of template fields structures.
|
| /kernel/linux/linux-4.19/Documentation/driver-model/ |
| D | driver.txt | 10 Device drivers are statically allocated structures. Though there may
45 The most common example of this are device ID structures. A driver
47 of these structures and the semantics for comparing device IDs are
49 sacrifice type-safety, so we keep bus-specific structures around.
156 it's a version the driver can handle, that driver data structures can
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | IMA-templates.rst | 25 definition of two new data structures: a template descriptor, to determine
29 Managing templates with these structures is very simple. To support
36 by translating the format into an array of template fields structures taken
53 method for each item of the array of template fields structures.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ext4/ |
| D | checksums.rst | 7 and jbd2 data structures. The associated feature flag is metadata\_csum.
10 structures did not have space to fit a full 32-bit checksum, so only the
13 structures. However, existing 32-bit filesystems cannot be extended to
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ext4/ondisk/ |
| D | checksums.rst | 7 and jbd2 data structures. The associated feature flag is metadata\_csum.
10 structures did not have space to fit a full 32-bit checksum, so only the
13 structures. However, existing 32-bit filesystems cannot be extended to
|
| /kernel/linux/linux-4.19/arch/mips/include/asm/sn/ |
| D | klconfig.h | 15 * The KLCONFIG structures store info about the various BOARDs found
23 * will depend on the format of the data structures in this file. In
74 #define SIZE_PAD 4096 /* 4k padding for structures */
114 /* Structures to manage various data storage areas */
223 * There are 2 different structures to represent these boards -
224 * lboard - Local board, rboard - remote board. These 2 structures
291 * Like BOARD structures, REMOTE ERRINFO structures can be built locally
296 * manipulating the structures, is that, the NODE number information should
301 * Note that these structures do not provide much info about connectivity.
306 * The data structures below define the above concepts.
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/sn/ |
| D | klconfig.h | 15 * The KLCONFIG structures store info about the various BOARDs found
23 * will depend on the format of the data structures in this file. In
74 #define SIZE_PAD 4096 /* 4k padding for structures */
114 /* Structures to manage various data storage areas */
223 * There are 2 different structures to represent these boards -
224 * lboard - Local board, rboard - remote board. These 2 structures
291 * Like BOARD structures, REMOTE ERRINFO structures can be built locally
296 * manipulating the structures, is that, the NODE number information should
301 * Note that these structures do not provide much info about connectivity.
306 * The data structures below define the above concepts.
[all …]
|