Home
last modified time | relevance | path

Searched refs:reservations (Results 1 – 22 of 22) sorted by relevance

/Linux-v5.4/Documentation/vm/
Dhugetlbfs_reserv.rst64 region in the reserv_map may indicate reservations exist for the
65 range, or reservations do not exist.
70 Indicates this task is the owner of the reservations
114 was specified, then this routine returns immediately as no reservations
124 in which reservations are represented in the reservation map.
127 exists or did exist for the corresponding page. As reservations are
130 a reservation exists for the corresponding page. As reservations are
132 reservation map can also be used to determine which reservations have
137 to indicate this VMA owns the reservations.
139 The reservation map is consulted to determine how many huge page reservations
[all …]
/Linux-v5.4/Documentation/filesystems/
Docfs2.txt89 resv_level=2 (*) Set how aggressive allocation reservations will be.
90 Valid values are between 0 (reservations off) to 8
91 (maximum space for reservations).
92 dir_resv_level= (*) By default, directory reservations will scale with file
93 reservations - users should rarely need to change this
94 value. If allocation reservations are turned off, this
Dxfs-delayed-logging-design.txt530 space available in the log if we are to use static reservations, and that is
626 the amount of space available in the log for their reservations. The practical
/Linux-v5.4/drivers/staging/uwb/
Drsv.c580 list_add_tail(&rsv->rc_node, &rc->reservations); in uwb_rsv_establish()
649 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_rsv_handle_drp_avail_change()
768 list_add_tail(&rsv->rc_node, &rc->reservations); in uwb_rsv_new_target()
813 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_rsv_find()
836 list_for_each_entry_safe(rsv, t, &rc->reservations, rc_node) { in uwb_rsv_update_all()
922 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_rsv_alien_bp_work()
949 list_for_each_entry_safe(rsv, t, &rc->reservations, rc_node) { in uwb_rsv_remove_all()
962 list_for_each_entry_safe(rsv, t, &rc->reservations, rc_node) { in uwb_rsv_remove_all()
970 INIT_LIST_HEAD(&rc->reservations); in uwb_rsv_init()
Duwb-debug.c201 list_for_each_entry(rsv, &rc->reservations, rc_node) { in reservations_show()
228 DEFINE_SHOW_ATTRIBUTE(reservations);
Ddrp.c101 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_rc_send_all_drp_ie()
127 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_rc_send_all_drp_ie()
371 list_for_each_entry(rsv, &rc->reservations, rc_node) { in uwb_drp_handle_all_conflict_rsv()
Duwb.h389 struct list_head reservations; member
/Linux-v5.4/fs/ocfs2/
DMakefile31 reservations.o \
/Linux-v5.4/Documentation/block/
Dpr.rst16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
Dbiodoc.rst1132 8.9. VM reservations patch (Ben LaHaise)
/Linux-v5.4/Documentation/filesystems/nfs/
Dpnfs-scsi-server.txt20 option and the underlying SCSI device support persistent reservations.
/Linux-v5.4/fs/jffs2/
DTODO5 reservations will necessarily be pessimistic. With this we could even
/Linux-v5.4/fs/btrfs/
Dblock-group.h135 atomic_t reservations; member
Dblock-group.c329 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()
330 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()
356 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
Dextent-tree.c2722 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
/Linux-v5.4/Documentation/powerpc/
Dfirmware-assisted-dump.rst280 file will change to reflect the new memory reservations.
/Linux-v5.4/Documentation/filesystems/caching/
Dnetfs-api.txt617 those pages will need to have any marks and reservations removed. This can be
804 backed by a cache, -EOPNOTSUPP if the cache doesn't support reservations,
/Linux-v5.4/drivers/staging/wusbcore/Documentation/
Dwusb-design-overview.rst271 higher layers will enable the higher layers to use the reservations upon
/Linux-v5.4/Documentation/scheduler/
Dsched-deadline.rst769 showing how SCHED_DEADLINE reservations can be created by a real-time
/Linux-v5.4/Documentation/driver-api/usb/
Dusb.rst926 With the Linux-USB stack, periodic bandwidth reservations use the
/Linux-v5.4/Documentation/x86/
Dresctrl_ui.rst971 end up allocating the same bits so the reservations are shared instead of
/Linux-v5.4/arch/x86/
DKconfig1738 trust the BIOS to get all its memory reservations and usages