Searched refs:latencies (Results 1 – 25 of 31) sorted by relevance
12
10 the service quality. Extreme latencies are caused by TCP's19 streams provoke high latencies when using TCP is unfortunate.33 to experience high retransmission latencies.
209 packet latencies.
155 zfcp_sdev->latencies.write.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()156 zfcp_sdev->latencies.write.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()157 zfcp_sdev->latencies.read.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()158 zfcp_sdev->latencies.read.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()159 zfcp_sdev->latencies.cmd.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()160 zfcp_sdev->latencies.cmd.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()161 spin_lock_init(&zfcp_sdev->latencies.lock); in zfcp_scsi_slave_alloc()
259 struct zfcp_latencies latencies; member
372 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \403 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \
2026 lat = &zfcp_sdev->latencies.read; in zfcp_fsf_req_trace()2031 lat = &zfcp_sdev->latencies.write; in zfcp_fsf_req_trace()2034 lat = &zfcp_sdev->latencies.cmd; in zfcp_fsf_req_trace()2039 spin_lock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()2043 spin_unlock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()
6 perf-sched - Tool to trace/measure scheduler properties (latencies)20 'perf sched latency' to report the per task scheduling latencies
21 read, write and setup latencies. Minimum valid values are 1. Controllers24 read, write and setup latencies. Controllers without setup latency control
10 throughput. It will still provide good latencies most of the17 latencies.
9 by varying exit latencies and power consumption during idle.
21 service time for a request. As we focus mainly on read latencies, this is
26 throughput and acceptable latencies.
18 channels. With a post 2.6.9 Linux kernel, latencies down to 64 (1.33 ms) or
117 the address space, each with varying latencies. This enables
24 determinism and well-bound latencies. Even in the worst-case, PI will
183 slowdowns and noticeable latencies. Normally Speedstep should be used
155 differentiated by varying exit latencies and power
216 latencies. But if it is too small slave won't be able to capture clear edge
51 process. This is necessary in order to preserve the memory latencies.
97 which can be used to tune the scheduler from "desktop" (i.e., low latencies) to
193 o Calculating latencies between two events
17 It can be used for debugging or analyzing latencies and324 disabled and enabled respectively) that caused the latencies:461 latencies, as described in "Latency1315 - you are experiencing weird latencies but it's difficult to
68 in realtime kernels in order to avoid excessive scheduling latencies.
215 work to a tasklet (bottom half) to keep system latencies low. You'll
199 but the overall latencies have been significantly improved by this separation.