| /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 | 369 unsigned long j, bool lazy) in rcu_nocb_do_flush_bypass() argument
391 if (lazy && rhp) { in rcu_nocb_do_flush_bypass()
413 unsigned long j, bool lazy) in rcu_nocb_flush_bypass() argument
419 return rcu_nocb_do_flush_bypass(rdp, rhp, j, lazy); in rcu_nocb_flush_bypass()
487 bool lazy) in rcu_nocb_try_bypass() argument
532 if (rdp->nocb_nobypass_count < nocb_nobypass_lim_per_jiffy && !lazy) { in rcu_nocb_try_bypass()
550 if (!rcu_nocb_flush_bypass(rdp, rhp, j, lazy)) { in rcu_nocb_try_bypass()
578 if (lazy) in rcu_nocb_try_bypass()
594 if (!ncbs || (bypass_is_lazy && !lazy)) { in rcu_nocb_try_bypass()
660 unsigned long flags, bool lazy) in call_rcu_nocb() argument
[all …]
|
| H A D | tree.h | 509 unsigned long j, bool lazy);
511 unsigned long flags, bool lazy);
|
| H A D | Kconfig | 339 bool "RCU callback lazy invocation functionality"
356 bool "Turn RCU lazy invocation off by default"
|
| H A D | tree.c | 3156 bool lazy; in __call_rcu_common() local
3187 lazy = lazy_in && !rcu_async_should_hurry(); in __call_rcu_common()
3203 call_rcu_nocb(rdp, head, 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
|
| H A D | unevictable-lru.rst | 168 might be), the lock action (e.g. SHM_LOCK) can be lazy, and need not populate
|
| /linux/kernel/ |
| H A D | irq_work.c | 186 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
189 lazy = this_cpu_ptr(&lazy_list); in irq_work_needs_cpu()
192 if (llist_empty(lazy)) in irq_work_needs_cpu()
|
| /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/drivers/gpu/drm/nouveau/ |
| H A D | nouveau_fence.h | 32 int nouveau_fence_wait(struct nouveau_fence *, bool lazy, bool intr);
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-probe.txt | 171 3) Define event based on source file with lazy pattern
182 'FUNC' specifies a probed function name, and it may have one of the following options; '+OFFS' is the offset from function entry address in bytes, ':RLN' is the relative-line number from function entry line, and '%return' means that it probes function return. And ';PTN' means lazy matching pattern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In addition, '@SRC' specifies a source file which has that function.
183 It is also possible to specify a probe point by the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is the source file path, ':ALN' is the line number and ';PTN' is the lazy matching pattern.
235 The lazy line matching is similar to glob matching but ignoring spaces in both of pattern and target. So this accepts wildcards('*', '?') and character classes(e.g. [a-z], [!A-Z]).
|
| /linux/drivers/gpu/drm/vmwgfx/ |
| H A D | vmwgfx_fence.c | 230 int vmw_fence_obj_wait(struct vmw_fence_obj *fence, bool lazy, in vmw_fence_obj_wait() argument
476 ret = vmw_fence_obj_wait(fence, arg->lazy, true, timeout); in vmw_fence_obj_wait_ioctl()
|
| /linux/include/uapi/drm/ |
| H A D | vmwgfx_drm.h | 647 __s32 lazy; member
|
| /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/Documentation/driver-api/driver-model/ |
| H A D | devres.rst | 30 that's probably because libata low level driver developers are 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/arch/powerpc/ |
| H A D | transactional_memory.rst | 94 Examples are glibc's getpid() and lazy symbol resolution.
|
| /linux/include/hyperv/ |
| H A D | hvgdk_mini.h | 684 u64 lazy : 1; member
|
| /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
|
| /linux/Documentation/locking/ |
| H A D | ww-mutex-design.rst | 350 The Wound-Wait preemption is implemented with a lazy-preemption scheme:
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 444 | furthermore important to wait on it, as this lazy approach is far |
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 2363 “lazy” variant of call_rcu() that might one day be created for
2376 structures is to leave the door open to “lazy” callbacks whose
2379 non-lazy callbacks decreases significantly for some important workload.
|
| /linux/Documentation/admin-guide/ |
| H A D | spkguide.txt | 125 manual uses the term keypad instead of numeric keypad. Also I'm lazy
|
| /linux/kernel/sched/ |
| H A D | core.c | 8099 PREEMPT_MODEL_ACCESSOR(lazy);
|