Searched refs:allocation (Results 51 – 75 of 453) sorted by relevance
12345678910>>...19
/openbmc/linux/scripts/coccinelle/api/alloc/ |
H A D | alloc_cast.cocci | 2 /// Remove casting the values returned by memory allocation functions 122 msg="WARNING: casting value returned by memory allocation function to (%s *) is useless." % (t)
|
/openbmc/linux/scripts/coccinelle/free/ |
H A D | devm_free.cocci | 10 /// containing the allocation function. It is thus necessary to make the 11 /// connection between the allocation function and the freeing function.
|
/openbmc/linux/fs/dlm/ |
H A D | midcomms.h | 20 gfp_t allocation, char **ppc);
|
/openbmc/linux/Documentation/core-api/ |
H A D | dma-attributes.rst | 98 optimize allocation (avoid coming up with large pages) instead of 110 This tells the DMA-mapping subsystem to suppress allocation failure reports 113 On some architectures allocation failures are reported with error messages 120 where allocation failures are not a problem, and shouldn't bother the logs.
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/dvb-apps/files/dvb-scan-table/dvb-t/ |
H A D | nz-Dunedin | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-AucklandWaiatarua | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-Hamilton | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-Waikato | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-Manawatu | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-WellingtonKaukau | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-WellingtonNgarara | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-Tauranga | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-Christchurch | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-AucklandInfill | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-HawkesBayNapier | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-HawkesBayMtErin | 3 # Channel allocation details for NZ can be found at
|
H A D | nz-WellingtonInfill | 3 # Channel allocation details for NZ can be found at
|
/openbmc/linux/Documentation/translations/zh_CN/mm/ |
H A D | index.rst | 17 (Documentation/translations/zh_CN/core-api/memory-allocation.rst)。
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | ext4.rst | 79 * improved file allocation (multi-block alloc) 89 * inode allocation using large virtual block groups via flex_bg 90 * delayed allocation 174 main file system. Enabling this mode will disable delayed allocation 194 delayed allocation even older data can be lost on power failure since 290 Defer block allocation until just before ext4 writes out the block(s) 291 in question. This allows ext4 to better allocation decisions more 295 Disable delayed allocation. Blocks are allocated when the data is 368 corrupted allocation bitmaps which cause blocks to be allocated which 433 modes. Enabling this mode will disable delayed allocation and O_DIRECT [all …]
|
/openbmc/linux/Documentation/networking/ |
H A D | mctp.rst | 167 specified will cause an allocation of a tag, if no valid tag is already 170 outgoing message. If any previous allocation has been performed (to for a 171 different remote EID), that allocation is lost. 225 In these cases, the ioctls allow you to decouple the tag allocation (and 259 allocation, and the ``tag`` value must match exactly the tag returned from the 260 allocation (including the ``MCTP_TAG_OWNER`` and ``MCTP_TAG_PREALLOC`` bits).
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 223.out | 92 base:allocation 103 base:allocation 113 base:allocation 214 base:allocation 225 base:allocation 235 base:allocation
|
/openbmc/linux/Documentation/gpu/ |
H A D | drm-mm.rst | 92 principles. Buffer allocation and read and write operations, described 98 contents or purpose, such as buffer allocation or synchronization 104 - Memory allocation and freeing 108 Buffer object allocation is relatively straightforward and largely 124 object allocation. 137 GEM splits creation of GEM objects and allocation of the memory that 160 Drivers are responsible for the actual physical pages allocation by 163 object, or to delay allocation until the memory is needed (for instance 167 Anonymous pageable memory allocation is not always desired, for instance 295 allocation scheme, drivers can allocate pages at fault time, or can
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/fuse-exfat/ |
H A D | fuse-exfat_1.4.0.bb | 3 extended file allocation table as a filesystem in userspace. A mounthelper \
|
/openbmc/linux/Documentation/fault-injection/ |
H A D | fault-injection.rst | 13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...) 17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...) 154 specifies the minimum page allocation order to be injected 350 - Inject slab allocation failures into module init/exit code:: 385 - Inject page allocation failures only for a specific module:: 473 allocation failure:: 484 Same as above except to inject page allocation failure instead of slab 485 allocation failure::
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | cafe_ccic.rst | 40 perhaps decreases the chances of an allocation failure later on. 43 option is only consulted for load-time allocation; when buffers are
|
12345678910>>...19