Searched full:structure (Results 1 – 25 of 685) sorted by relevance
12345678910>>...28
| /Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 15 Data-Structure Relationships
27 This diagram shows an enclosing ``rcu_state`` structure containing a tree
31 This structure is adjusted at boot time, if needed, to handle the common
47 structure.
105 structure need advance to the ``rcu_node`` structure at the next level
106 up the tree. This means that at the leaf-level ``rcu_node`` structure,
113 period will progress all the way to the root ``rcu_node`` structure,
115 structure remains acceptably low.
138 are protected by the corresponding root ``rcu_node`` structure's lock.
139 #. Each ``rcu_node`` structure has a spinlock.
[all …]
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 9 information from the kernel like structure size, page size, symbol
36 data structure used to store information returned by the uname(2) system
87 Makedumpfile gets the pglist_data structure from this symbol, which is
95 The address of the mem_section array, its length, structure size, and
110 The size of a page structure. struct page is an important data structure
116 The size of a pglist_data structure. This value is used to check if the
117 pglist_data structure is valid. It is also used for checking the memory
123 The size of a zone structure. This value is used to check if the zone
124 structure has been found. It is also used for excluding free pages.
129 The size of a free_area structure. It indicates whether the free_area
[all …]
|
| /Documentation/arch/powerpc/ |
| D | qe_firmware.rst | 18 V - Firmware Structure Layout
89 structure signals the microcode which of these virtual traps is active.
91 This structure contains 6 words that the application should copy to some
92 specific been defined. This table describes the structure::
121 and has special instructions for the s/w associated with it. This structure is
166 V - Firmware Structure Layout
183 This structure supports versioning, where the version of the structure is
184 embedded into the structure itself. To ensure forward and backwards
185 compatibility, all versions of the structure must use the same 'qe_header'
186 structure at the beginning.
[all …]
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 190 with the current task structure and releases corresponding shared
195 structure, where as unshare() operates on the current active
206 new namespace structure, the error return code will have to
209 structure, which may not exist anymore.
212 current context structure was moved into new dup_* functions. Now,
215 task structure that is being constructed. unshare() system call on
220 2) For each context structure, call the corresponding unshare()
222 structure, if the appropriate bit is set in the flags argument.
225 are new context structures then lock the current task structure,
226 associate new context structures with the current task structure,
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 14 data, the structure size weren't enough to fit, and just extending its
27 ``dvb_frontend_parameters`` structure:
58 structure:
74 for cable QAM frontend you use the ``dvb_qam_parameters`` structure:
91 ATSC frontends are supported by the ``dvb_vsb_parameters`` structure:
106 DVB-T frontends are supported by the ``dvb_ofdm_parameters`` structure:
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 114 consist of simple null-terminated strings with the following structure::
122 structure. Currently expected to be "1".
158 - `target`: The fully qualified name of the target data structure
229 Managing structure size changes
232 A data structure can be partially opaque to modules if its allocation is
235 structure without breaking the ABI, as long as the layout for the original
240 hide the increase in structure size. The `byte_size` rule allows us to
241 override the structure size used for symbol versioning.
246 - `target`: The fully qualified name of the target data structure
248 - `value`: A positive decimal number indicating the structure size
[all …]
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 67 DVD_READ_STRUCT Read structure
68 DVD_WRITE_STRUCT Write structure
154 cdrom_msf structure, describing a segment of music to play
185 cdrom_ti structure, describing a segment of music to play
214 cdrom_tochdr structure
218 cdrom_tochdr structure
239 cdrom_tocentry structure
243 cdrom_tocentry structure
375 cdrom_volctrl structure containing volumes for up to 4
425 cdrom_subchnl structure
[all …]
|
| /Documentation/hid/ |
| D | hiddev.rst | 94 the value that it was changed to. Note that the structure is defined
122 hiddev_devinfo structure.
138 Gets a hiddev_devinfo structure which describes the device.
179 Fills in a hiddev_report_info structure for the user. The report is
188 filled into the returned hiddev_report_info structure.
194 hiddev_field_info structure. The user must fill in report_id and
195 report_type in this structure, as above. The field_index should also
202 Returns the usage_code in a hiddev_usage_ref structure, given that
204 field have already been filled into the structure.
209 Returns the value of a usage in a hiddev_usage_ref structure. The
[all …]
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 37 a linked RCU-protected data structure, and phase two frees that element.
50 critical section for the ``rcu_node`` structure's
62 Therefore, for any given ``rcu_node`` structure, any access
118 | But the chain of rcu_node-structure lock acquisitions guarantees |
166 | by the CPU's leaf ``rcu_node`` structure's ``->lock`` as described |
194 the ``rcu_node`` structure's ``->lock`` field, so much so that it is
247 The box represents the ``rcu_node`` structure's ``->lock`` critical
283 RCU-protected data structure). It simply enqueues the ``rcu_head``
284 structure on a per-CPU list, which cannot become associated with a grace
305 ``rcu_node`` structure's ``->lock``. In all cases, there is full
[all …]
|
| /Documentation/crypto/ |
| D | crypto_engine.rst | 12 You must put, at the start of your transform context your_tfm_ctx, the structure
24 has access to the transform structure. It is not possible to access the context
26 structure "``struct your_tfm_ctx``". The engine assumes (requires) the placement
55 Note that these functions access the crypto_async_request structure
|
| D | userspace-if.rst | 103 filled struct sockaddr data structure. This data structure must be
142 initialization, the struct sockaddr data structure must be filled as
160 specified with the data structure provided by the sendmsg() system call.
163 struct cmsghdr data structure. See recv(2) and cmsg(3) for more
164 information on how the cmsghdr data structure is used together with the
165 send/recv system call family. That cmsghdr data structure holds the
196 initialization, the struct sockaddr data structure must be filled as
219 specified with the data structure provided by the sendmsg() system call.
222 struct cmsghdr data structure. See recv(2) and cmsg(3) for more
223 information on how the cmsghdr data structure is used together with the
[all …]
|
| D | intro.rst | 13 of its structure is given. Based on the architecture, the API can be
53 provided with a structure, which contains a transformation object (TFM).
55 The structure that contains transformation objects may also be referred
69 API calls that refer to the data structure type a consumer is expected
|
| /Documentation/core-api/ |
| D | padata.rst | 26 padata_instance structure for overall control of how jobs are to be run::
84 padata_priv structure, which represents one job::
92 This structure will almost certainly be embedded within some larger
93 structure specific to the work to be done. Most of its fields are private to
94 padata, but the structure should be zeroed at initialisation time, and the
118 function gets the padata_priv structure pointer as its lone parameter;
120 container_of() to find the enclosing structure.
137 serial() function in the padata_priv structure. That call will happen on
165 job by defining a padata_mt_job structure, which is explained in the Interface
|
| D | debug-objects.rst | 21 debugobjects is not changing the data structure of the real object so it
28 A kernel subsystem needs to provide a data structure which describes the
30 data structure to describe the object type needs at minimum the name of
54 pointer to the object type specific debug description structure.
77 structure if provided by the caller. The fixup function can correct the
100 structure if provided by the caller. The fixup function can correct the
124 structure if provided by the caller. The fixup function can correct the
163 fixup_destroy function of the object type description structure if
179 the object type description structure if provided by the caller. The
194 fixup_assert_init of the object type description structure provided by
[all …]
|
| D | kobject.rst | 25 usually embedded within some other structure which contains the stuff
28 No structure should **EVER** have more than one kobject embedded within it.
32 - A ktype is the type of object that embeds a kobject. Every structure
60 direct expression of inheritance, so other techniques - such as structure
68 So, for example, the UIO code in ``drivers/uio/uio.c`` has a structure that
76 If you have a struct uio_map structure, finding its embedded kobject is
79 what is the pointer to the containing structure? You must avoid tricks
80 (such as assuming that the kobject is at the beginning of the structure)
88 * ``type`` is the type of the containing structure, and
89 * ``member`` is the name of the structure field to which ``pointer`` points.
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | pvtime.rst | 39 Return value: (int64) IPA of the stolen time data structure for this
47 meaningfully filled by the hypervisor (see structure below).
49 PV_TIME_ST returns the structure for the calling VCPU.
54 The structure pointed to by the PV_TIME_ST hypercall is as follows:
70 All values in the structure are stored little-endian.
72 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
75 structure per VCPU of the guest.
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-rkisp1.rst | 30 The buffer contains a single instance of the C structure
31 :c:type:`rkisp1_params_cfg` defined in ``rkisp1-config.h``. So the structure can
50 The buffer contains a single instance of the C structure
52 :c:type:`rkisp1_ext_params_cfg` structure is designed to allow userspace to
72 instance of the C structure :c:type:`rkisp1_stat_buffer` defined in
73 ``rkisp1-config.h``. So the structure can be obtained from the buffer by:
|
| D | vidioc-g-crop.rst | 39 ``type`` field of a struct :c:type:`v4l2_crop` structure to the
41 with a pointer to this structure. The driver fills the rest of the
42 structure or returns the ``EINVAL`` error code if cropping is not supported.
46 v4l2_crop structure and call the :ref:`VIDIOC_S_CROP <VIDIOC_G_CROP>` ioctl with a pointer
47 to this structure.
|
| /Documentation/filesystems/ |
| D | files.rst | 28 table are in a separate structure - struct fdtable.
32 expansion of fdtable, a new fdtable structure is allocated
33 and files->fdtab points to the new structure. The fdtable
34 structure is freed with RCU and lock-free readers either
37 the fdtable structure -
64 4. To look up the file structure given an fd, a reader
|
| /Documentation/virt/kvm/x86/ |
| D | msr.rst | 26 structure::
65 a copy of the following structure::
80 updates of this structure is arbitrary and implementation-dependent.
81 The hypervisor may update this structure at any time it sees fit until
93 of the update of this structure. Guests can subtract this value
95 structure update.
99 time at the time this structure was last updated. Unit is
197 following structure::
265 hold a copy of the following structure::
278 updates of this structure is arbitrary and implementation-dependent.
[all …]
|
| /Documentation/driver-api/ |
| D | miscellaneous.rst | 33 are expected to embed this structure in a driver-specific structure.
34 This structure contains fields that describe a particular chip.
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 37 Structure of a V4L driver
40 All drivers have the following structure:
66 Structure of the V4L2 framework
69 The framework closely resembles the driver structure: it has a v4l2_device
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 2 kernel data structure for DRBD-9
5 This describes the in kernel data structure for DRBD-9. Starting with
6 Linux v3.14 we are reorganizing DRBD to use this data structure.
8 Basic Data Structure
|
| /Documentation/staging/ |
| D | magic-number.rst | 7 add a magic number to a structure, you should also add it to this
12 numbers. This allows you to check at run time whether (a) a structure
13 has been clobbered, or (b) you've passed the wrong structure to a
20 the structure, like so::
69 Magic Name Number Structure File
|
| /Documentation/mm/ |
| D | free_page_reporting.rst | 11 it will allocate and initialize a page_reporting_dev_info structure. The
12 field within the structure it will populate is the "report" function
32 page_reporting_dev_info structure that is currently in use by free page
|
12345678910>>...28