| /OK3568_Linux_fs/kernel/Documentation/RCU/Design/Data-Structures/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/ |
| H A 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 …]
|
| /OK3568_Linux_fs/buildroot/package/libnet/ |
| H A D | 0001-Use-standard-int64_t-instead-of-__int64_t-for-mingw-cross-build.patch | 12 include/libnet/libnet-structures.h | 6 +++---
15 diff --git a/include/libnet/libnet-structures.h b/include/libnet/libnet-structures.h
17 --- a/include/libnet/libnet-structures.h
18 +++ b/include/libnet/libnet-structures.h
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | io_uring.h | 19 * A number of the io_uring structures get used in other core kernel
20 * structures, only as "opaque" pointers, so there is not any real ABI
21 * breakage. But, due to the visibility of the structures going away, the
26 * view, we need to keep around the "old" io_uring structures for the CRC
32 * structures that any code uses, but so life is in the world of stable
34 * The real structures are in io_uring/io_uring.c, see the ones there if
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A 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
|
| H A 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.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/stabs/ |
| H A D | Enumerations.html | 27 <link href="Structures.html#Structures" rel="next" title="Structures">
65 Next: <a href="Structures.html#Structures" accesskey="n" rel="next">Structures</a>, Previous: <a hr…
123 Next: <a href="Structures.html#Structures" accesskey="n" rel="next">Structures</a>, Previous: <a hr…
|
| H A D | Typedefs.html | 28 <link href="Structures.html#Structures" rel="previous" title="Structures">
65 … rel="next">Unions</a>, Previous: <a href="Structures.html#Structures" accesskey="p" rel="previous…
|
| H A D | Structures.html | 15 <title>STABS: Structures</title>
17 <meta name="description" content="STABS: Structures">
18 <meta name="keywords" content="STABS: Structures">
62 <a name="Structures"></a>
68 <a name="Structures-1"></a>
69 <h3 class="section">5.8 Structures</h3>
71 <p>The encoding of structures in stabs can be shown with an example.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/stabs/ |
| H A D | Enumerations.html | 27 <link href="Structures.html#Structures" rel="next" title="Structures">
65 Next: <a href="Structures.html#Structures" accesskey="n" rel="next">Structures</a>, Previous: <a hr…
123 Next: <a href="Structures.html#Structures" accesskey="n" rel="next">Structures</a>, Previous: <a hr…
|
| H A D | Typedefs.html | 28 <link href="Structures.html#Structures" rel="previous" title="Structures">
65 … rel="next">Unions</a>, Previous: <a href="Structures.html#Structures" accesskey="p" rel="previous…
|
| H A D | Structures.html | 15 <title>STABS: Structures</title>
17 <meta name="description" content="STABS: Structures">
18 <meta name="keywords" content="STABS: Structures">
62 <a name="Structures"></a>
68 <a name="Structures-1"></a>
69 <h3 class="section">5.8 Structures</h3>
71 <p>The encoding of structures in stabs can be shown with an example.
|
| /OK3568_Linux_fs/kernel/fs/xfs/libxfs/ |
| H A 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 …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/host_include/openssl/ |
| H A D | pkcs7.h | 30 // structures (RFC 2315).
42 // certificates in SignedData structures are unordered. Callers should not
54 // certificates in SignedData structures are unordered. The order in |certs|
65 // SignedData structures are unordered. Callers should not assume an order in
71 // in SignedData structures are unordered. The order in |crls| will not be
81 // certificates in SignedData structures are unordered. Callers should not
93 // SignedData structures are unordered. Callers should not assume an order in
210 // certificates in SignedData structures are unordered. The order of |certs|
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/include/openssl/ |
| H A D | pkcs7.h | 30 // structures (RFC 2315).
42 // certificates in SignedData structures are unordered. Callers should not
54 // certificates in SignedData structures are unordered. The order in |certs|
65 // SignedData structures are unordered. Callers should not assume an order in
71 // in SignedData structures are unordered. The order in |crls| will not be
81 // certificates in SignedData structures are unordered. Callers should not
93 // SignedData structures are unordered. Callers should not assume an order in
210 // certificates in SignedData structures are unordered. The order of |certs|
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/include/openssl/ |
| H A D | pkcs7.h | 30 // structures (RFC 2315).
42 // certificates in SignedData structures are unordered. Callers should not
54 // certificates in SignedData structures are unordered. The order in |certs|
65 // SignedData structures are unordered. Callers should not assume an order in
71 // in SignedData structures are unordered. The order in |crls| will not be
81 // certificates in SignedData structures are unordered. Callers should not
93 // SignedData structures are unordered. Callers should not assume an order in
210 // certificates in SignedData structures are unordered. The order of |certs|
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/host_include/openssl/ |
| H A D | pkcs7.h | 30 // structures (RFC 2315).
42 // certificates in SignedData structures are unordered. Callers should not
54 // certificates in SignedData structures are unordered. The order in |certs|
65 // SignedData structures are unordered. Callers should not assume an order in
71 // in SignedData structures are unordered. The order in |crls| will not be
81 // certificates in SignedData structures are unordered. Callers should not
93 // SignedData structures are unordered. Callers should not assume an order in
210 // certificates in SignedData structures are unordered. The order of |certs|
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/device-mapper/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/scripts/gcc-plugins/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/arch/mips/include/asm/sn/ |
| H A 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 …]
|
| /OK3568_Linux_fs/u-boot/include/dm/ |
| H A D | root.h | 86 * dm_init_and_scan() - Initialise Driver Model structures and scan for devices
90 * This calls dm_init() to set up Driver Model structures.
99 * dm_init() - Initialise Driver Model structures
110 * dm_uninit - Uninitialise Driver Model structures
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/fs/xfs/ |
| H A 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()
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/arch/arm64/kvm/vgic/ |
| H A D | vgic-init.c | 22 * structures.
31 * structures that depend on sizing information (number of CPUs,
33 * structures. Can be executed lazily for GICv2.
45 * kvm_vgic_early_init() - Initialize static VGIC VCPU data structures
48 * Only do initialization of static structures that don't require any
127 * kvm_vgic_dist_init: initialize the dist data structures
178 * structures and register VCPU-specific KVM iodevs
245 * vgic_init: allocates and initializes dist and vcpu data structures
|