| /linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 6 structures (linked_list, rbtree), with particular focus on the verifier's
7 implementation of semantics specific to those data structures.
14 these graph data structures. **No guarantees** of stability for either
24 The BPF map API has historically been the main way to expose data structures
25 of various types for use within BPF programs. Some data structures fit naturally
27 interacting with the latter group of data structures can be hard to parse
32 BPF allocator, it is now possible to implement BPF data structures whose API
35 Two such data structures - linked_list and rbtree - have many verification
41 structures.
46 Data structures implemente
[all...] |
| /linux/Documentation/staging/ |
| H A D | magic-number.rst | 8 file, since it is best if the magic numbers used by various structures
11 It is a **very** good idea to protect kernel data structures with magic
15 passing pointers to structures via a void * pointer. The tty code,
17 discipline-specific structures back and forth.
30 structures following the array have been overwritten. Using this
|
| /linux/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
|
| /linux/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...] |
| /linux/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
|
| H A D | planar-apis.rst | 19 Some of the V4L2 API calls and structures are interpreted differently,
35 in multi-planar API structures), while the single-planar API cannot
48 New structures for describing multi-planar formats are added: struct
|
| /linux/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
|
| H A D | kcopyd.rst | 16 To start a copy job, the user must set up io_region structures to describe
20 copy are given as an array of io_region structures::
|
| /linux/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
[all...] |
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-dmi-tables | 5 The firmware provides DMI structures as a packed list of
10 The format of SMBIOS entry point and DMI structures
|
| H A D | sysfs-bus-coreboot | 6 access data structures created by the Coreboot BIOS.
13 and contains tagged data structures to be shared with payloads
|
| /linux/Documentation/filesystems/ext4/ |
| H A 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
|
| /linux/Documentation/gpu/ |
| H A D | vga-switcheroo.rst | 34 Public structures
55 Private structures
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | coreboot.txt | 4 bookkeeping structures to the kernel. Since coreboot itself cannot boot a
18 coreboot to dynamically allocate data structures that remain resident.
|
| /linux/drivers/message/fusion/lsi/ |
| H A D | mpi_history.txt | 122 * Added structures for FwHeader and DataHeader.
158 * structures.
175 * 08-30-05 01.05.10 Added 4 new events and their event data structures.
262 * Added definitions and structures for IOC Page 2 and
302 * Added structures for Manufacturing Page 4, IO Unit
363 * Added new extended config pages types and structures for
395 * 12-07-04 01.05.04 Added config page structures for BIOS Page 2, RAID
421 * Added defines and structures for the new Log Page 0, a
542 * 09-28-01 01.02.03 Added structures and defines for SCSI Enclosure
564 * 06-24-05 01.05.05 Added SCSI IO 32 structures an
[all...] |
| /linux/Documentation/filesystems/ |
| H A D | hfsplus.rst | 23 that have uninitialized permissions structures.
28 that have uninitialized permissions structures.
|
| /linux/Documentation/networking/device_drivers/ethernet/huawei/ |
| H A D | hinic3.rst | 45 hinic3_queue_common.[ch] Common structures and methods for NIC queues
52 hinic3_wq.[ch] Work queue data structures and interface
54 hinic3_hwdev.[ch] HW structures and methods abstractions
61 hinic3_nic_dev.h NIC structures and methods abstractions
|
| /linux/security/ |
| H A D | Kconfig.hardening | 247 menu "Hardening of kernel data structures"
263 data corruption in kernel memory structures when they get checked
277 prompt "Randomize layout of sensitive kernel structures"
281 If you enable this, the layouts of structures that are entirely
283 __no_randomize_layout), or structures that have been explicitly
311 structures as much as possible, which may have both a
326 Randomization of sensitive kernel structures will make a
329 in structures. This reduces the performance hit of RANDSTRUCT
|
| /linux/Documentation/driver-api/media/ |
| H A D | v4l2-tveeprom.rst | 3 Hauppauge TV EEPROM functions and data structures
|
| H A D | v4l2-mediabus.rst | 3 V4L2 Media Bus functions and data structures
|
| H A D | v4l2-mc.rst | 3 V4L2 Media Controller functions and data structures
|
| H A D | v4l2-flash-led-class.rst | 3 V4L2 flash functions and data structures
|
| H A D | v4l2-mem2mem.rst | 3 V4L2 Memory to Memory functions and data structures
|
| /linux/Documentation/fb/ |
| H A D | cmap_xfbdev.rst | 5 These notes explain how X's dix layer uses fbdev's cmap structures.
7 - example of relevant structures in fbdev as used for a 3-bit grayscale cmap::
|
| /linux/Documentation/mm/ |
| H A D | slab.rst | 7 Functions and structures
|