/linux-4.1.27/drivers/xen/ |
D | balloon.c | 331 struct xen_memory_reservation reservation = { in increase_reservation() local 359 set_xen_guest_handle(reservation.extent_start, frame_list); in increase_reservation() 360 reservation.nr_extents = nr_pages; in increase_reservation() 361 rc = HYPERVISOR_memory_op(XENMEM_populate_physmap, &reservation); in increase_reservation() 402 struct xen_memory_reservation reservation = { in decrease_reservation() local 464 set_xen_guest_handle(reservation.extent_start, frame_list); in decrease_reservation() 465 reservation.nr_extents = nr_pages; in decrease_reservation() 466 ret = HYPERVISOR_memory_op(XENMEM_decrease_reservation, &reservation); in decrease_reservation()
|
/linux-4.1.27/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-4.1.27/drivers/dma-buf/ |
D | Makefile | 1 obj-y := dma-buf.o fence.o reservation.o seqno-fence.o
|
/linux-4.1.27/drivers/usb/wusbcore/ |
D | Makefile | 15 reservation.o \
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | sysfs-devices-system-xen_memory | 47 memory reservation to. 62 reservation.
|
/linux-4.1.27/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 …]
|
D | ext3.txt | 94 reservation
|
/linux-4.1.27/arch/x86/xen/ |
D | setup.c | 207 struct xen_memory_reservation reservation = { in xen_free_mfn() local 213 set_xen_guest_handle(reservation.extent_start, &mfn); in xen_free_mfn() 214 reservation.nr_extents = 1; in xen_free_mfn() 216 return HYPERVISOR_memory_op(XENMEM_decrease_reservation, &reservation); in xen_free_mfn()
|
/linux-4.1.27/drivers/gpu/drm/omapdrm/ |
D | TODO | 13 . This can be handled by the dma-buf fence/reservation stuff when it
|
/linux-4.1.27/Documentation/DocBook/ |
D | .device-drivers.xml.cmd | 2 …inux/fence.h include/linux/seqno-fence.h drivers/dma-buf/reservation.c include/linux/reservation.h…
|
/linux-4.1.27/arch/mips/kvm/ |
D | 00README.txt | 25 LL/TLBP/SC. Since the TLBP instruction causes a trap the reservation gets cleared
|
/linux-4.1.27/fs/jffs2/ |
D | TODO | 7 make the reservation.
|
/linux-4.1.27/drivers/of/ |
D | Kconfig | 85 Helpers to allow for reservation of memory regions
|
/linux-4.1.27/Documentation/locking/ |
D | ww-mutex-design.txt | 28 to be locked, the caller would be assigned a unique reservation id/ticket, 30 associated with a execbuf, the one with the lowest reservation ticket (i.e. 31 the oldest task) wins, and the one with the higher reservation id (i.e. the 47 trying to acquire locks doesn't grab a new reservation id, but keeps the one it
|
/linux-4.1.27/Documentation/usb/ |
D | WUSB-Design-overview.txt | 250 availability information will be used by the bandwidth reservation 253 The bandwidth reservation routines are in progress and are thus not 255 to initiate DRP reservation requests through interaction with sysfs. DRP 256 reservation requests from remote UWB devices will also be handled. The 259 completion. [Note: The bandwidth reservation work is in progress and
|
/linux-4.1.27/Documentation/vm/ |
D | transhuge.txt | 53 - it doesn't require memory reservation and in turn it uses hugepages 54 whenever possible (the only possible reservation here is kernelcore= 65 if compared to the reservation approach of hugetlbfs by allowing all 67 entities). It doesn't require reservation to prevent hugepage
|
/linux-4.1.27/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
|
D | netfs-api.txt | 802 (*) Data space reservation: 810 If size is given as zero then the reservation will be cancelled.
|
/linux-4.1.27/Documentation/target/ |
D | tcm_mod_builder.txt | 22 SPC-3 persistent reservation are automatically generated in $TCM_NEW_MOD/$TCM_NEW_MOD_fabric.c
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-deadline.txt | 395 With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation 397 You can also use schedtool to create a reservation for an already running 490 /* This creates a 10ms/30ms reservation */
|
/linux-4.1.27/Documentation/powerpc/ |
D | firmware-assisted-dump.txt | 13 - Fadump uses the same firmware interfaces and memory reservation model
|
/linux-4.1.27/arch/m68k/ |
D | Kconfig.machine | 185 int "Memory reservation (MiB)"
|
/linux-4.1.27/fs/ext4/ |
D | extents.c | 4539 int reservation = allocated_clusters - in ext4_ext_map_blocks() local 4582 EXT4_C2B(sbi, reservation)); in ext4_ext_map_blocks() 4584 ei->i_reserved_data_blocks += reservation; in ext4_ext_map_blocks()
|
/linux-4.1.27/Documentation/scsi/ |
D | ChangeLog.megaraid | 192 megaraid: reservation reset failed
|
D | ChangeLog.lpfc | 481 reservation conflicts, etc 1386 * Free irq reservation and kill running timers when insmod or
|
/linux-4.1.27/Documentation/ |
D | pinctrl.txt | 1406 The above has to be done from process context. The reservation of the pins
|
/linux-4.1.27/ |
D | MAINTAINERS | 3266 F: include/linux/reservation.h
|