| /Linux-v5.4/Documentation/block/ |
| D | pr.rst | 26 Only the initiator that owns the reservation can write to the
30 Only the initiator that owns the reservation can access the
44 All initiators with a registered key are considered reservation
46 Please reference the SPC spec on the meaning of a reservation
51 All initiators with a registered key are considered reservation
53 Please reference the SPC spec on the meaning of a reservation
63 This ioctl command registers a new reservation if the new_key argument
64 is non-null. If no existing reservation exists old_key must be zero,
65 if an existing reservation should be replaced old_key must contain
66 the old reservation key.
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 67 These are stored in the bottom bits of the reservation map pointer.
78 reservation must be restored when the huge page is freed. More
88 semantics of the reservation map is significantly different for the two types
91 - For private mappings, the reservation map hangs off the VMA structure.
94 - For shared mappings, the reservation map hangs off the inode. Specifically,
97 contains a reservation map. As a result, the reservation map is allocated
124 in which reservations are represented in the reservation map.
126 - For shared mappings, an entry in the reservation map indicates a reservation
128 consumed, the reservation map is not modified.
129 - For private mappings, the lack of an entry in the reservation map indicates
[all …]
|
| D | transhuge.rst | 29 - it doesn't require memory reservation and in turn it uses hugepages
30 whenever possible (the only possible reservation here is kernelcore=
|
| /Linux-v5.4/drivers/xen/ |
| D | mem-reservation.c | 95 struct xen_memory_reservation reservation = { in xenmem_reservation_increase() local
102 set_xen_guest_handle(reservation.extent_start, frames); in xenmem_reservation_increase()
103 reservation.nr_extents = count; in xenmem_reservation_increase()
104 return HYPERVISOR_memory_op(XENMEM_populate_physmap, &reservation); in xenmem_reservation_increase()
111 struct xen_memory_reservation reservation = { in xenmem_reservation_decrease() local
118 set_xen_guest_handle(reservation.extent_start, frames); in xenmem_reservation_decrease()
119 reservation.nr_extents = count; in xenmem_reservation_decrease()
120 return HYPERVISOR_memory_op(XENMEM_decrease_reservation, &reservation); in xenmem_reservation_decrease()
|
| D | Makefile | 4 obj-y += mem-reservation.o
|
| D | Kconfig | 168 driver in that proper memory reservation is made by
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-fs-xfs | 24 represents the total log reservation of all currently
35 represents the total log reservation of all currently
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | dma-buf.rst | 14 one device as finished access, and (3) reservation, which manages the
121 .. kernel-doc:: drivers/dma-buf/reservation.c
124 .. kernel-doc:: drivers/dma-buf/reservation.c
127 .. kernel-doc:: include/linux/reservation.h
|
| /Linux-v5.4/drivers/staging/wusbcore/ |
| D | Makefile | 16 reservation.o \
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-devices-system-xen_memory | 47 memory reservation to.
62 reservation.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 50 a special log reservation known as a permanent transaction reservation. A
53 of reservation size limitations. Hence a rolling extent removal transaction
478 The big issue for a checkpoint transaction is the log space reservation for the
486 usage of the transaction. The reservation accounts for log record headers,
502 space. From this, it should be obvious that a static log space reservation is
506 Further, if we are going to use a static reservation, which bit of the entire
507 reservation does it cover? We account for space used by the transaction
508 reservation by tracking the space currently used by the object in the CIL and
510 relogged. This allows for a checkpoint reservation to only have to account for
513 However, even using a static reservation for just the log metadata is
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/omapdrm/ |
| D | TODO | 13 . This can be handled by the dma-buf fence/reservation stuff when it
|
| /Linux-v5.4/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smem.txt | 15 Definition: handle to memory reservation for main SMEM memory region.
|
| /Linux-v5.4/arch/x86/xen/ |
| D | setup.c | 238 struct xen_memory_reservation reservation = { in xen_free_mfn() local
244 set_xen_guest_handle(reservation.extent_start, &mfn); in xen_free_mfn()
245 reservation.nr_extents = 1; in xen_free_mfn()
247 return HYPERVISOR_memory_op(XENMEM_decrease_reservation, &reservation); in xen_free_mfn()
|
| /Linux-v5.4/arch/mips/kvm/ |
| D | 00README.txt | 25 LL/TLBP/SC. Since the TLBP instruction causes a trap the reservation gets cleared
|
| /Linux-v5.4/Documentation/locking/ |
| D | ww-mutex-design.rst | 29 to be locked, the caller would be assigned a unique reservation id/ticket,
31 associated with a execbuf, the one with the lowest reservation ticket (i.e.
32 the oldest task) wins, and the one with the higher reservation id (i.e. the
36 In the RDBMS literature, a reservation ticket is associated with a transaction.
64 trying to acquire locks doesn't grab a new reservation id, but keeps the one it
|
| /Linux-v5.4/fs/jffs2/ |
| D | TODO | 7 make the reservation.
|
| /Linux-v5.4/drivers/staging/wusbcore/Documentation/ |
| D | wusb-design-overview.rst | 263 availability information will be used by the bandwidth reservation
266 The bandwidth reservation routines are in progress and are thus not
268 to initiate DRP reservation requests through interaction with sysfs. DRP
269 reservation requests from remote UWB devices will also be handled. The
272 completion. [Note: The bandwidth reservation work is in progress and
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | firmware-assisted-dump.rst | 14 - Fadump uses the same firmware interfaces and memory reservation model
147 Contiguous Memory Allocator (CMA) for memory reservation if CMA is
148 configured for kernel. With CMA reservation this memory will be
|
| /Linux-v5.4/Documentation/target/ |
| D | tcm_mod_builder.rst | 24 SPC-3 persistent reservation are automatically generated in $TCM_NEW_MOD/$TCM_NEW_MOD_fabric.c
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | backend-api.txt | 395 taken as request to cancel a reservation.
400 The reservation may exceed the current size of the object, thus permitting
402 exceed the reservation, it's permitted to refuse requests to allocate
403 pages, but not required. An object may be pruned down to its reservation
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-deadline.rst | 178 are the reservation parameters.
295 is of the same order of magnitude of the reservation period. In such cases,
758 With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation
760 You can also use schedtool to create a reservation for an already running
853 /* This creates a 10ms/30ms reservation */
|
| /Linux-v5.4/fs/xfs/libxfs/ |
| D | xfs_alloc.c | 2034 xfs_extlen_t reservation; /* blocks that are still reserved */ in xfs_alloc_space_available() local
2041 reservation = xfs_ag_resv_needed(pag, args->resv); in xfs_alloc_space_available()
2045 longest = xfs_alloc_longest_free_extent(pag, min_free, reservation); in xfs_alloc_space_available()
2056 reservation - min_free - args->minleft); in xfs_alloc_space_available()
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 59 if compared to the reservation approach of hugetlbfs by allowing all
61 entities). It doesn't require reservation to prevent hugepage
|
| /Linux-v5.4/arch/m68k/ |
| D | Kconfig.machine | 188 int "Memory reservation (MiB)"
|
