/openbmc/linux/tools/testing/selftests/bpf/progs/ |
H A D | test_pinning.c | 11 __uint(pinning, LIBBPF_PIN_BY_NAME); 26 __uint(pinning, LIBBPF_PIN_NONE);
|
H A D | test_sk_assign.c | 26 __uint(pinning, LIBBPF_PIN_BY_NAME); 41 __u32 pinning; member 47 .pinning = PIN_GLOBAL_NS,
|
H A D | test_pinning_invalid.c | 11 __uint(pinning, 2); /* invalid */
|
/openbmc/linux/Documentation/admin-guide/LSM/ |
H A D | LoadPin.rst | 17 LoadPin starts pinning when it sees the first file loaded. If the 19 created to toggle pinning: ``/proc/sys/kernel/loadpin/enabled``. (Having 20 a mutable filesystem means pinning is mutable too, but having the
|
/openbmc/linux/samples/bpf/ |
H A D | tc_l2_redirect_kern.c | 30 __u32 pinning; member 44 .pinning = PIN_GLOBAL_NS,
|
H A D | test_cgrp2_tc.bpf.c | 23 __uint(pinning, LIBBPF_PIN_BY_NAME);
|
H A D | lwt_len_hist.bpf.c | 20 __uint(pinning, LIBBPF_PIN_BY_NAME);
|
/openbmc/linux/Documentation/infiniband/ |
H A D | user_verbs.rst | 47 Memory pinning 52 ib_uverbs module manages pinning and unpinning memory regions via
|
/openbmc/qemu/docs/ |
H A D | rdma.txt | 52 Use of RDMA during migration requires pinning and registering memory 79 Note: for very large virtual machines (hundreds of GBs), pinning all 84 still gain from the benefits of advanced pinning with RDMA. 166 (Memory is not released from pinning until the migration 381 After pinning, an RDMA Write is generated and transmitted 411 are not compatible with infiniband memory pinning and will result in
|
/openbmc/linux/security/loadpin/ |
H A D | Kconfig | 18 If selected, LoadPin will enforce pinning at boot. If not
|
/openbmc/linux/Documentation/core-api/ |
H A D | pin_user_pages.rst | 153 because DAX pages do not have a separate page cache, and so "pinning" implies 165 avoid pinning entirely (this is ideal), as follows: register for mmu notifier 197 page_maybe_dma_pinned(): the whole point of pinning 221 a "more severe" form of pinning. And finally, FOLL_LONGTERM is an even more
|
/openbmc/linux/Documentation/networking/ |
H A D | msg_zerocopy.rst | 21 Copy avoidance is not a free lunch. As implemented, with page pinning, 26 Page pinning also changes system call semantics. It temporarily shares
|
/openbmc/linux/drivers/infiniband/ |
H A D | Kconfig | 57 memory regions without pinning their pages, fetching the
|
/openbmc/linux/Documentation/filesystems/caching/ |
H A D | fscache.rst | 245 ACCES Number of accesses pinning the cache 274 ACC Number of accesses pinning the cache
|
/openbmc/linux/Documentation/driver-api/ |
H A D | vfio.rst | 463 use of the vfio page pinning interface must implement this callback in 635 and the handling of those includes pinning/unpinning pages and updating 637 The v2 IOMMU splits accounting and pinning into separate operations: 647 IOMMU table and do not do pinning; instead these check that the userspace
|
/openbmc/linux/Documentation/admin-guide/mm/ |
H A D | memory-hotplug.rst | 582 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all. 632 - Long-term pinning of pages. Techniques that rely on long-term pinnings 636 have to be migrated off that zone while pinning. Pinning a page can fail 639 In addition, using ZONE_MOVABLE might make page pinning more expensive,
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-delayed-logging-design.rst | 261 locked while we sleep could end up pinning the tail of the log before there is 869 pending transactions. Thus the pinning and unpinning of a log item is symmetric 876 log item completion. The result of this is that pinning and unpinning of the 882 pinning and unpinning becomes symmetric around a checkpoint context. We have to 890 for the pin count means that the pinning of an item must take place under the 893 the fact pinning the item is dependent on whether the item is present in the 896 (or not pinning, as the case may be). Hence we must hold the CIL flush/commit 924 relatively long period of time - the pinning of log items needs to be done 928 separately to the pinning of objects could be used to reduce the hold time of
|
/openbmc/linux/tools/lib/bpf/ |
H A D | libbpf_internal.h | 273 __u32 pinning; member
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | sva.rst | 16 by the device, it also doesn't require pinning pages for DMA. 256 pinning requirement for memory.
|
/openbmc/linux/Documentation/userspace-api/ |
H A D | iommufd.rst | 165 iopt_pages which avoids multi-pinning and double accounting of page
|
/openbmc/linux/Documentation/mm/ |
H A D | transhuge.rst | 40 address of the page and its temporary pinning to release after the I/O
|
/openbmc/linux/Documentation/virt/kvm/ |
H A D | locking.rst | 138 kvm_vcpu_gfn_to_pfn_atomic, before the cmpxchg. After the pinning:
|
/openbmc/linux/fs/f2fs/ |
H A D | segment.c | 2659 unsigned int *newseg, bool new_sec, bool pinning) in get_new_segment() argument 2684 segno = pinning ? 0 : max(first_zoned_segno(sbi), *newseg); in get_new_segment() 2799 bool pinning = type == CURSEG_COLD_DATA_PINNED; in new_curseg() local 2805 get_new_segment(sbi, &segno, new_sec, pinning); in new_curseg() 2806 if (new_sec && pinning && in new_curseg()
|
/openbmc/linux/Documentation/admin-guide/sysctl/ |
H A D | fs.rst | 197 from "pinning" vulnerable setuid/setgid files against being upgraded by
|
/openbmc/linux/tools/bpf/bpftool/Documentation/ |
H A D | bpftool-prog.rst | 162 support autoattach, bpftool falls back to regular pinning
|