| /linux-6.3-rc2/tools/testing/selftests/bpf/progs/ |
| A D | test_pinning.c | 11 __uint(pinning, LIBBPF_PIN_BY_NAME);
26 __uint(pinning, LIBBPF_PIN_NONE);
|
| A D | test_sk_assign.c | 25 __uint(pinning, LIBBPF_PIN_BY_NAME);
40 __u32 pinning; member
46 .pinning = PIN_GLOBAL_NS,
|
| A D | test_pinning_invalid.c | 11 __uint(pinning, 2); /* invalid */
|
| /linux-6.3-rc2/Documentation/admin-guide/LSM/ |
| 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
|
| /linux-6.3-rc2/samples/bpf/ |
| A D | tc_l2_redirect_kern.c | 30 __u32 pinning; member
44 .pinning = PIN_GLOBAL_NS,
|
| A D | test_cgrp2_tc.bpf.c | 23 __uint(pinning, LIBBPF_PIN_BY_NAME);
|
| A D | lwt_len_hist.bpf.c | 20 __uint(pinning, LIBBPF_PIN_BY_NAME);
|
| /linux-6.3-rc2/Documentation/infiniband/ |
| A D | user_verbs.rst | 47 Memory pinning
52 ib_uverbs module manages pinning and unpinning memory regions via
|
| /linux-6.3-rc2/security/loadpin/ |
| A D | Kconfig | 18 If selected, LoadPin will enforce pinning at boot. If not
|
| /linux-6.3-rc2/Documentation/core-api/ |
| A D | pin_user_pages.rst | 147 because DAX pages do not have a separate page cache, and so "pinning" implies
159 avoid pinning entirely (this is ideal), as follows: register for mmu notifier
191 page_maybe_dma_pinned(): the whole point of pinning
215 a "more severe" form of pinning. And finally, FOLL_LONGTERM is an even more
|
| /linux-6.3-rc2/drivers/infiniband/ |
| A D | Kconfig | 57 memory regions without pinning their pages, fetching the
|
| /linux-6.3-rc2/Documentation/networking/ |
| 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
|
| /linux-6.3-rc2/Documentation/filesystems/caching/ |
| A D | fscache.rst | 245 ACCES Number of accesses pinning the cache
274 ACC Number of accesses pinning the cache
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | vfio.rst | 330 use of the vfio page pinning interface must implement this callback in
502 and the handling of those includes pinning/unpinning pages and updating
504 The v2 IOMMU splits accounting and pinning into separate operations:
514 IOMMU table and do not do pinning; instead these check that the userspace
|
| /linux-6.3-rc2/Documentation/admin-guide/mm/ |
| A D | memory-hotplug.rst | 562 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all.
612 - Long-term pinning of pages. Techniques that rely on long-term pinnings
616 have to be migrated off that zone while pinning. Pinning a page can fail
619 In addition, using ZONE_MOVABLE might make page pinning more expensive,
|
| /linux-6.3-rc2/tools/lib/bpf/ |
| A D | libbpf_internal.h | 258 __u32 pinning; member
|
| A D | linker.c | 1541 if (main_def->pinning != extra_def->pinning) { in map_defs_match()
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| 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
|
| /linux-6.3-rc2/Documentation/x86/ |
| A D | sva.rst | 16 by the device, it also doesn't require pinning pages for DMA.
256 pinning requirement for memory.
|
| /linux-6.3-rc2/Documentation/userspace-api/ |
| A D | iommufd.rst | 165 iopt_pages which avoids multi-pinning and double accounting of page
|
| /linux-6.3-rc2/Documentation/mm/ |
| A D | transhuge.rst | 40 address of the page and its temporary pinning to release after the I/O
|
| /linux-6.3-rc2/kernel/module/ |
| A D | Kconfig | 232 load pinning security policy is enabled.
|
| /linux-6.3-rc2/Documentation/virt/kvm/ |
| A D | locking.rst | 131 kvm_vcpu_gfn_to_pfn_atomic, before the cmpxchg. After the pinning:
|
| /linux-6.3-rc2/tools/bpf/bpftool/Documentation/ |
| A D | bpftool-prog.rst | 161 support autoattach, bpftool falls back to regular pinning
|
| /linux-6.3-rc2/Documentation/admin-guide/sysctl/ |
| A D | fs.rst | 197 from "pinning" vulnerable setuid/setgid files against being upgraded by
|