/linux-6.12.1/drivers/gpu/drm/i915/display/ |
D | intel_wm.c | 216 const u16 *latencies; in pri_wm_latency_show() local 219 latencies = dev_priv->display.wm.skl_latency; in pri_wm_latency_show() 221 latencies = dev_priv->display.wm.pri_latency; in pri_wm_latency_show() 223 wm_latency_show(m, latencies); in pri_wm_latency_show() 231 const u16 *latencies; in spr_wm_latency_show() local 234 latencies = dev_priv->display.wm.skl_latency; in spr_wm_latency_show() 236 latencies = dev_priv->display.wm.spr_latency; in spr_wm_latency_show() 238 wm_latency_show(m, latencies); in spr_wm_latency_show() 246 const u16 *latencies; in cur_wm_latency_show() local 249 latencies = dev_priv->display.wm.skl_latency; in cur_wm_latency_show() [all …]
|
/linux-6.12.1/Documentation/block/ |
D | kyber-iosched.rst | 5 The only two tunables for the Kyber scheduler are the target latencies for 7 these target latencies.
|
D | deadline-iosched.rst | 20 service time for a request. As we focus mainly on read latencies, this is
|
/linux-6.12.1/Documentation/networking/ |
D | tcp-thin.rst | 14 the service quality. Extreme latencies are caused by TCP's 23 streams provoke high latencies when using TCP is unfortunate. 37 to experience high retransmission latencies.
|
D | bridge.rst | 217 latencies when a host leaves a multicast group or channel. 224 is thus bound only by the packet transmission latencies in the multiaccess
|
/linux-6.12.1/drivers/s390/scsi/ |
D | zfcp_scsi.c | 151 zfcp_sdev->latencies.write.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 152 zfcp_sdev->latencies.write.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 153 zfcp_sdev->latencies.read.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 154 zfcp_sdev->latencies.read.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 155 zfcp_sdev->latencies.cmd.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 156 zfcp_sdev->latencies.cmd.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc() 157 spin_lock_init(&zfcp_sdev->latencies.lock); in zfcp_scsi_slave_alloc()
|
D | zfcp_def.h | 285 struct zfcp_latencies latencies; member
|
D | zfcp_fsf.c | 2362 lat = &zfcp_sdev->latencies.read; in zfcp_fsf_req_trace() 2367 lat = &zfcp_sdev->latencies.write; in zfcp_fsf_req_trace() 2370 lat = &zfcp_sdev->latencies.cmd; in zfcp_fsf_req_trace() 2375 spin_lock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace() 2379 spin_unlock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()
|
D | zfcp_sysfs.c | 551 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \ 582 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \
|
/linux-6.12.1/Documentation/trace/ |
D | hwlat_detector.rst | 9 detect large system latencies induced by the behavior of certain underlying 22 you are trying to keep event service latencies down in the microsecond range. 57 change to a default of 10 usecs. If any latencies that exceed the threshold is
|
/linux-6.12.1/block/ |
D | Kconfig.iosched | 15 multiqueue and other fast devices. Given target latencies for reads and
|
/linux-6.12.1/tools/perf/Documentation/ |
D | perf-kwork.txt | 6 perf-kwork - Tool to trace/measure kernel work properties (latencies) 22 'perf kwork latency' to report the per kwork latencies.
|
D | perf-sched.txt | 6 perf-sched - Tool to trace/measure scheduler properties (latencies) 20 'perf sched latency' to report the per task scheduling latencies
|
/linux-6.12.1/Documentation/devicetree/bindings/powerpc/opal/ |
D | power-mgt.txt | 60 - ibm,cpu-idle-state-latencies-ns: 62 exit-latencies (in ns) for the idle states in
|
/linux-6.12.1/Documentation/tools/rtla/ |
D | common_timerlat_options.rst | 30 Set the /dev/cpu_dma_latency to *us*, aiming to bound exit from idle latencies.
|
/linux-6.12.1/kernel/ |
D | Kconfig.preempt | 23 throughput. It will still provide good latencies most of the 30 latencies.
|
/linux-6.12.1/Documentation/staging/ |
D | speculation.rst | 10 To improve performance and minimize average latencies, many contemporary CPUs
|
/linux-6.12.1/Documentation/admin-guide/device-mapper/ |
D | statistics.rst | 19 histogram of latencies. All these counters may be accessed by sending 74 collect histogram of latencies. The
|
/linux-6.12.1/Documentation/driver-api/ |
D | pps.rst | 75 you should take into account the latencies and jitter introduced by 246 latencies. But if it is too small slave won't be able to capture clear edge
|
/linux-6.12.1/Documentation/sound/cards/ |
D | emu10k1-jack.rst | 20 channels. With a post 2.6.9 Linux kernel, latencies down to 64 (1.33 ms) or
|
/linux-6.12.1/Documentation/timers/ |
D | no_hz.rst | 96 in order to avoid degrading from-idle transition latencies. 231 eliminate scheduling-clock interrupt latencies. Here are some 245 to degrade your latencies -- and that this degradation can
|
/linux-6.12.1/Documentation/dev-tools/ |
D | gpio-sloppy-logic-analyzer.rst | 30 Note that this is a last resort analyzer which can be affected by latencies,
|
/linux-6.12.1/arch/sh/mm/ |
D | Kconfig | 122 the address space, each with varying latencies. This enables
|
/linux-6.12.1/fs/erofs/ |
D | Kconfig | 168 async decompression for low latencies on some architectures.
|
/linux-6.12.1/Documentation/locking/ |
D | pi-futex.rst | 25 determinism and well-bound latencies. Even in the worst-case, PI will
|