| /linux/Documentation/translations/zh_CN/mm/ |
| H A D | active_mm.rst | 64 计数器,即有多少 “真正的地址空间用户”,另一个是 “mm_count”计数器,即 “lazy” 68 一个lazy的用户仍在活动,所以你实际上得到的情况是,你有一个地址空间 **只** 69 被lazy的用户使用。这通常是一个短暂的生命周期状态,因为一旦这个线程被安排给一 73 “init_mm”应该被认为只是一个 “没有其他上下文时的lazy上下文”,事实上,它主
|
| /linux/kernel/rcu/ |
| H A D | tree_nocb.h | 309 unsigned long j, bool lazy) in rcu_nocb_do_flush_bypass() argument 331 if (lazy && rhp) { in rcu_nocb_do_flush_bypass() 353 unsigned long j, bool lazy) in rcu_nocb_flush_bypass() argument 359 return rcu_nocb_do_flush_bypass(rdp, rhp, j, lazy); in rcu_nocb_flush_bypass() 395 bool lazy) in rcu_nocb_try_bypass() argument 439 if (rdp->nocb_nobypass_count < nocb_nobypass_lim_per_jiffy && !lazy) { in rcu_nocb_try_bypass() 460 if (!rcu_nocb_flush_bypass(rdp, rhp, j, lazy)) { in rcu_nocb_try_bypass() 488 if (lazy) in rcu_nocb_try_bypass() 504 if (!ncbs || (bypass_is_lazy && !lazy)) { in rcu_nocb_try_bypass() 596 rcu_callback_t func, unsigned long flags, bool lazy) in call_rcu_nocb() argument [all …]
|
| H A D | tree.h | 505 unsigned long j, bool lazy); 507 rcu_callback_t func, unsigned long flags, bool lazy);
|
| H A D | tree.c | 3094 bool lazy; in __call_rcu_common() local 3125 lazy = lazy_in && !rcu_async_should_hurry(); in __call_rcu_common() 3141 call_rcu_nocb(rdp, head, func, flags, lazy); in __call_rcu_common()
|
| /linux/Documentation/mm/ |
| H A D | active_mm.rst | 5 Note, the mm_count refcount may no longer include the "lazy" users 7 with CONFIG_MMU_LAZY_TLB_REFCOUNT=n. Taking and releasing these lazy 63 and a "mm_count" counter that is the number of "lazy" users (ie anonymous 67 user exited on another CPU while a lazy user was still active, so you do 69 lazy users. That is often a short-lived state, because once that thread 74 more. "init_mm" should be considered just a "lazy context when no other
|
| /linux/drivers/crypto/intel/qat/qat_common/ |
| H A D | icp_qat_hw_20_comp.h | 69 __u16 lazy; member 102 QAT_FIELD_SET(val32, csr.lazy, in ICP_QAT_FW_COMP_20_BUILD_CONFIG_UPPER()
|
| /linux/drivers/opp/ |
| H A D | opp.h | 207 struct list_head node, lazy; member 268 return unlikely(!list_empty(&opp_table->lazy)); in lazy_linking_pending()
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 30 The NEON/VFP register file is managed using lazy preserve (on UP systems) and 31 lazy restore (on both SMP and UP systems). This means that the register file is 45 mode will hit the lazy restore trap upon next use. This is handled by the
|
| /linux/drivers/gpu/drm/nouveau/ |
| H A D | nouveau_fence.h | 32 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
|
| H A D | nouveau_fence.c | 323 nouveau_fence_wait(struct nouveau_fence *fence, bool lazy, bool intr) in nouveau_fence_wait() argument 327 if (!lazy) in nouveau_fence_wait()
|
| /linux/mm/ |
| H A D | vmalloc.c | 939 struct rb_list lazy; member 2350 if (RB_EMPTY_ROOT(&vn->lazy.root)) in __purge_vmap_area_lazy() 2353 spin_lock(&vn->lazy.lock); in __purge_vmap_area_lazy() 2354 WRITE_ONCE(vn->lazy.root.rb_node, NULL); in __purge_vmap_area_lazy() 2355 list_replace_init(&vn->lazy.head, &vn->purge_list); in __purge_vmap_area_lazy() 2356 spin_unlock(&vn->lazy.lock); in __purge_vmap_area_lazy() 2453 spin_lock(&vn->lazy.lock); in free_vmap_area_noflush() 2454 insert_vmap_area(va, &vn->lazy.root, &vn->lazy.head); in free_vmap_area_noflush() 2455 spin_unlock(&vn->lazy.lock); in free_vmap_area_noflush() 5195 spin_lock(&vn->lazy.lock); in show_purge_info() [all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-probe.txt | 165 3) Define event based on source file with lazy pattern 176 …ine, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (s… 177 …ber or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, … 229 The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and targe…
|
| /linux/include/uapi/drm/ |
| H A D | vmwgfx_drm.h | 647 __s32 lazy; member
|
| /linux/Documentation/arch/x86/ |
| H A D | iommu.rst | 143 iommu: DMA domain TLB invalidation policy: lazy mode
|
| /linux/Documentation/arch/parisc/ |
| H A D | registers.rst | 18 CR10 (CCR) lazy FPU saving*
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 27 umounted. Note that detaching (or lazy umounting) the filesystem 213 filesystem is still attached (it hasn't been lazy unmounted)
|
| /linux/arch/ |
| H A D | Kconfig | 545 # "lazy tlb" beyond its final refcount (i.e., by the time __mmdrop frees the mm 551 # the lazy tlb reference of a kthread's ->active_mm (non-arch code has been 558 # mm as a lazy tlb beyond its last reference count, by shooting down these 560 # be using the mm as a lazy tlb, so that they may switch themselves to using 562 # may be using mm as a lazy tlb mm. 566 # at least all possible CPUs in which the mm is lazy.
|
| /linux/Documentation/filesystems/ |
| H A D | autofs-mount-control.rst | 23 Currently autofs uses "umount -l" (lazy umount) to clear active mounts 24 at restart. While using lazy umount works for most cases, anything that
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | devres.rst | 30 that's probably because libata low level driver developers are lazy
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_sched.rst | 187 This is not valid for the *lazy* variant of the flag, which causes only
|
| /linux/Documentation/arch/powerpc/ |
| H A D | transactional_memory.rst | 94 Examples are glibc's getpid() and lazy symbol resolution.
|
| /linux/drivers/iommu/ |
| H A D | Kconfig | 126 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
|
| /linux/include/hyperv/ |
| H A D | hvgdk_mini.h | 677 u64 lazy : 1; member
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numa_memory_policy.rst | 138 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs 140 Although hugetlbfs segments now support lazy allocation, their support
|
| /linux/arch/sparc/lib/ |
| H A D | checksum_32.S | 411 addx %g5, %g0, %g5 ! I am now to lazy to optimize this (question it
|