Searched full:hit (Results 1 – 25 of 87) sorted by relevance
1234
| /Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 12 The policy can return a simple HIT or MISS or issue a migration.
21 doesn't update states (eg, hit counts) for a block more than once
67 pointers. It avoids storing an explicit hit count for each block. It
79 based on their hit count (~ln(hit count)). This meant the bottom
84 smq does not maintain a hit count, instead it swaps hit entries with
91 The mq policy maintained a hit count for each cache block. For a
92 different block to get promoted to the cache its hit count has to
96 smq doesn't maintain hit counts, so a lot of this problem just goes
|
| D | writecache.rst | 84 6. the number of read blocks that hit the cache
86 8. the number of write blocks that hit uncommitted block
87 9. the number of write blocks that hit committed block
|
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | hit,hd44780.yaml | 4 $id: http://devicetree.org/schemas/auxdisplay/hit,hd44780.yaml#
22 const: hit,hd44780
88 compatible = "hit,hd44780";
114 compatible = "hit,hd44780";
|
| /Documentation/tools/rtla/ |
| D | rtla-timerlat-top.rst | 39 latency higher than *30 us* is hit. Finally, it is set to save the trace
40 buffer if the stop condition is hit::
70 timerlat hit stop tracing
113 timerlat/6-79756 [006] ....... 426.271267: timerlat_main: stop tracing hit on cpu 6
125 The primary reason for this high value is the wake-up path that was hit
|
| /Documentation/s390/ |
| D | 3270.rst | 212 and hit ENTER to execute them.
218 and more output will appear. You may hit ENTER with nothing typed in
220 which indicates no scrolling will occur. (If you hit ENTER with "Linux
231 Other things you may do when the log area fills up are: hit PA2 to
232 clear the log area and write more output to it, or hit CLEAR to clear
262 may hit PF10 again for the next-most-recent command, and so on. A
288 hit PF24. Want to see the command line first, before you execute it?
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-papr-pmem | 61 * "CchRHCnt" : Cache Read Hit Count
62 * "CchWHCnt" : Cache Write Hit Count
|
| /Documentation/trace/ |
| D | kprobes.rst | 31 routine to be invoked when the breakpoint is hit.
46 the probe is hit.
112 probe is hit, Kprobes saves a copy of the return address, and replaces
118 passes to the trampoline and that probe is hit. Kprobes' trampoline
148 function entry is hit, the user-defined entry_handler, if any, is invoked.
175 sysctl(8)), Kprobes tries to reduce probe-hit overhead by using a jump
237 it. If the to-be-optimized probepoint is hit before being optimized,
364 Sets a breakpoint at the address kp->addr. When the breakpoint is hit, Kprobes
368 aren't hit until calling enable_kprobe(kp).
402 the breakpoint was hit. Return 0 here unless you're a Kprobes geek.
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | pids.rst | 11 Since it is trivial to hit the task limit without hitting any kmemcg limits in
39 - max: Number of times fork failed because limit was hit.
|
| /Documentation/mm/ |
| D | remap_file_pages.rst | 31 One side effect of emulation (apart from performance) is that user can hit
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 19 In both modes, all writes to the array will hit cache disk first. This means
28 disks and it's possible the writes don't hit all RAID disks yet before the
|
| /Documentation/admin-guide/mm/ |
| D | ksm.rst | 154 that hit the deduplication limit for stale information.
157 scan. It's a noop if not a single KSM page hit the
173 the number of KSM pages that hit the ``max_page_sharing`` limit
|
| D | concepts.rst | 74 large memory working set will experience performance hit because of
82 improves TLB hit-rate and thus improves overall system performance.
|
| /Documentation/fault-injection/ |
| D | provoke-crashes.rst | 42 Indicates the number of times the crash point is to be hit
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 163 - Traps packets that the device decided to drop in case they hit a
227 - Traps packets that hit reject routes (i.e., "unreachable", "prohibit")
351 - Traps unicast packets that hit a local route and need to be locally
481 - Traps packets that the device decided to drop in case they hit a
525 - Contains packet traps for packets that hit an exception (e.g., TTL
|
| /Documentation/process/ |
| D | 8.Conclusion.rst | 41 somewhat obsolete by the time they hit the shelves, and they have been on
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 29 is hit, or sync() is called, or the kernel runs out of memory), the hope
|
| /Documentation/admin-guide/ |
| D | numastat.rst | 2 Numa policy hit/miss statistics
|
| D | sysrq.rst | 9 It is a 'magical' key combo you can hit which the kernel will respond to
215 I hit SysRq, but nothing seems to happen, what's wrong?
263 When I hit a SysRq key combination only the header appears on the console?
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 48 New submissions can be sent at any time, but if they intend to hit the
|
| /Documentation/networking/ |
| D | nf_flowtable.rst | 20 A packet that finds a matching entry in the flowtable (ie. flowtable hit) is
65 /hit\_no_| |
|
| D | nexthop-group-resilient.rst | 94 amount of time that a bucket must not be hit by traffic in order for it to
151 been hit by traffic.
155 as busy are treated as if traffic hit them.
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 10 operating system before data actually has hit the non-volatile storage. This
|
| /Documentation/driver-api/media/ |
| D | tx-rx.rst | 103 involvement in observing LP-11 or LP-111 state. 100 µs is a brief period to hit
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 40 bigger hit than the normal linear rule would do. (The solution of
|
| /Documentation/kbuild/ |
| D | kconfig.rst | 259 Next hit and Previous hit, respectively. Use <Esc> to
|
1234