Searched refs:spend (Results 1 – 20 of 20) sorted by relevance
| /linux-5.19.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_ctx.c | 397 ktime_t spend; in amdgpu_ctx_fini() local
399 spend = amdgpu_ctx_fini_entity(ctx->entities[i][j]); in amdgpu_ctx_fini()
400 atomic64_add(ktime_to_ns(spend), &mgr->time_spend[i]); in amdgpu_ctx_fini()
952 ktime_t spend; in amdgpu_ctx_mgr_usage() local
957 spend = amdgpu_ctx_entity_time(ctx, centity); in amdgpu_ctx_mgr_usage()
958 usage[hw_ip] = ktime_add(usage[hw_ip], spend); in amdgpu_ctx_mgr_usage()
|
| /linux-5.19.10/Documentation/x86/ |
| D | tlb.rst | 61 Essentially, you are balancing the cycles you spend doing invlpg
62 with the cycles that you spend refilling the TLB later.
|
| /linux-5.19.10/Documentation/block/ |
| D | deadline-iosched.rst | 65 may even know that it is a waste of time to spend any time attempting to
|
| /linux-5.19.10/Documentation/admin-guide/pm/ |
| D | strategies.rst | 45 typically the system can spend much more time in a sleep state than it can be
|
| D | cpuidle.rst | 106 idle states, or there is not enough time to spend in an idle state before the
136 spend in the given state, including the time needed to enter it (which may be
151 CPU depends on can spend in an idle state, including the time necessary to enter
234 does not occur any time soon, the hardware may spend indefinite amount of time
378 idle state "X" must reflect the minimum time to spend in idle state "MX" of
|
| D | sleep-states.rst | 35 working state), such that the processors can spend time in their deepest idle
|
| /linux-5.19.10/Documentation/trace/ |
| D | hwlat_detector.rst | 20 other tasks and those tasks can spend an inordinate amount of time in the
|
| /linux-5.19.10/Documentation/locking/ |
| D | lockstat.rst | 60 - total time we spend waiting on this lock
|
| /linux-5.19.10/drivers/gpu/drm/i915/ |
| D | Kconfig.profile | 79 we may spend some time polling for its completion. As the IRQ may
|
| /linux-5.19.10/Documentation/security/ |
| D | self-protection.rst | 88 made to kernel code mentioned above) that allow them to spend the rest
|
| /linux-5.19.10/Documentation/admin-guide/sysctl/ |
| D | net.rst | 423 The amount of time we will spend trying to resolve an Appletalk address.
|
| /linux-5.19.10/Documentation/driver-api/pm/ |
| D | cpuidle.rst | 183 Minimum time to spend in this idle state including the time needed to
|
| /linux-5.19.10/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 109 pages unless hugepages are immediately available. Clearly if we spend CPU
|
| /linux-5.19.10/Documentation/process/ |
| D | 5.Posting.rst | 82 up patches is a bit of an art; some developers spend a long time figuring
|
| /linux-5.19.10/Documentation/driver-api/media/drivers/ |
| D | zoran.rst | 385 rather want to spend some more money on better boards. In general, VIA
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 217 time (in microseconds) this cpu should spend in this idle state
|
| /linux-5.19.10/Documentation/vm/ |
| D | unevictable-lru.rst | 38 will spend a lot of time scanning the LRU lists looking for the small fraction
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | reporting-issues.rst | 284 Like most programmers, Linux kernel developers don't like to spend time dealing
783 programmers, Linux kernel developers don't like to spend time dealing with
1725 spend on maintenance work on the upstream kernel. Sometimes maintainers also
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | path-lookup.rst | 608 quite different from traditional locking, so we will spend a little extra
992 kernel spend too much time on just one path is one of them. With
|
| /linux-5.19.10/Documentation/virt/kvm/ |
| D | api.rst | 7101 scheduling during guest halts. The maximum time a VCPU can spend polling is
|