/linux-6.1.9/tools/testing/selftests/bpf/progs/ |
D | test_pinning.c | 11 __uint(pinning, LIBBPF_PIN_BY_NAME); 26 __uint(pinning, LIBBPF_PIN_NONE);
|
D | test_pinning_invalid.c | 11 __uint(pinning, 2); /* invalid */
|
D | test_sk_assign.c | 30 __u32 pinning; member 36 .pinning = PIN_GLOBAL_NS,
|
/linux-6.1.9/samples/bpf/ |
D | lwt_len_hist_kern.c | 26 __u32 pinning; member 33 .pinning = 2,
|
D | test_cgrp2_tc_kern.c | 30 __u32 pinning; member 37 .pinning = PIN_GLOBAL_NS,
|
D | tc_l2_redirect_kern.c | 30 __u32 pinning; member 44 .pinning = PIN_GLOBAL_NS,
|
/linux-6.1.9/Documentation/admin-guide/LSM/ |
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.1.9/Documentation/infiniband/ |
D | user_verbs.rst | 47 Memory pinning 52 ib_uverbs module manages pinning and unpinning memory regions via
|
/linux-6.1.9/tools/bpf/bpftool/Documentation/ |
D | common_options.rst | 30 about section names, changes pinning logic and doesn't support
|
/linux-6.1.9/security/loadpin/ |
D | Kconfig | 18 If selected, LoadPin will enforce pinning at boot. If not
|
/linux-6.1.9/Documentation/core-api/ |
D | pin_user_pages.rst | 148 because DAX pages do not have a separate page cache, and so "pinning" implies 160 avoid pinning entirely (this is ideal), as follows: register for mmu notifier 192 page_maybe_dma_pinned(): the whole point of pinning 216 a "more severe" form of pinning. And finally, FOLL_LONGTERM is an even more
|
/linux-6.1.9/drivers/infiniband/ |
D | Kconfig | 57 memory regions without pinning their pages, fetching the
|
/linux-6.1.9/Documentation/filesystems/caching/ |
D | fscache.rst | 245 ACCES Number of accesses pinning the cache 274 ACC Number of accesses pinning the cache
|
/linux-6.1.9/Documentation/networking/ |
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
|
D | rds.rst | 283 loopback, stats, usermem pinning, and the connection state machine.
|
/linux-6.1.9/Documentation/admin-guide/mm/ |
D | memory-hotplug.rst | 564 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all. 614 - Long-term pinning of pages. Techniques that rely on long-term pinnings 618 have to be migrated off that zone while pinning. Pinning a page can fail 621 In addition, using ZONE_MOVABLE might make page pinning more expensive,
|
/linux-6.1.9/tools/lib/bpf/ |
D | libbpf_internal.h | 258 __u32 pinning; member
|
D | linker.c | 1541 if (main_def->pinning != extra_def->pinning) { in map_defs_match()
|
/linux-6.1.9/Documentation/filesystems/ |
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.1.9/Documentation/driver-api/ |
D | vfio.rst | 464 and the handling of those includes pinning/unpinning pages and updating 466 The v2 IOMMU splits accounting and pinning into separate operations: 476 IOMMU table and do not do pinning; instead these check that the userspace
|
/linux-6.1.9/Documentation/x86/ |
D | sva.rst | 16 by the device, it also doesn't require pinning pages for DMA. 256 pinning requirement for memory.
|
/linux-6.1.9/Documentation/virt/kvm/ |
D | locking.rst | 119 kvm_vcpu_gfn_to_pfn_atomic, before the cmpxchg. After the pinning:
|
/linux-6.1.9/Documentation/mm/ |
D | transhuge.rst | 42 address of the page and its temporary pinning to release after the I/O
|
/linux-6.1.9/kernel/module/ |
D | Kconfig | 231 load pinning security policy is enabled.
|
/linux-6.1.9/Documentation/admin-guide/sysctl/ |
D | fs.rst | 228 from "pinning" vulnerable setuid/setgid files against being upgraded by
|