| /linux-4.1.27/Documentation/networking/ |
| D | tcp-thin.txt | 10 the service quality. Extreme latencies are caused by TCP's
19 streams provoke high latencies when using TCP is unfortunate.
33 to experience high retransmission latencies.
|
| D | README.ipw2100 | 209 packet latencies.
|
| /linux-4.1.27/drivers/s390/scsi/ |
| D | zfcp_scsi.c | 134 zfcp_sdev->latencies.write.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
135 zfcp_sdev->latencies.write.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
136 zfcp_sdev->latencies.read.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
137 zfcp_sdev->latencies.read.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
138 zfcp_sdev->latencies.cmd.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
139 zfcp_sdev->latencies.cmd.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()
140 spin_lock_init(&zfcp_sdev->latencies.lock); in zfcp_scsi_slave_alloc()
|
| D | zfcp_def.h | 256 struct zfcp_latencies latencies; member
|
| D | zfcp_sysfs.c | 383 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \
414 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \
|
| D | zfcp_fsf.c | 2002 lat = &zfcp_sdev->latencies.read; in zfcp_fsf_req_trace()
2007 lat = &zfcp_sdev->latencies.write; in zfcp_fsf_req_trace()
2010 lat = &zfcp_sdev->latencies.cmd; in zfcp_fsf_req_trace()
2015 spin_lock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()
2019 spin_unlock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()
|
| /linux-4.1.27/tools/perf/Documentation/ |
| 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-4.1.27/kernel/ |
| D | Kconfig.preempt | 10 throughput. It will still provide good latencies most of the
17 latencies.
|
| /linux-4.1.27/Documentation/cpuidle/ |
| D | core.txt | 9 by varying exit latencies and power consumption during idle.
|
| /linux-4.1.27/drivers/gpu/drm/i915/ |
| D | i915_debugfs.c | 3903 const uint16_t *latencies; in pri_wm_latency_show() local
3906 latencies = dev_priv->wm.skl_latency; in pri_wm_latency_show()
3908 latencies = to_i915(dev)->wm.pri_latency; in pri_wm_latency_show()
3910 wm_latency_show(m, latencies); in pri_wm_latency_show()
3919 const uint16_t *latencies; in spr_wm_latency_show() local
3922 latencies = dev_priv->wm.skl_latency; in spr_wm_latency_show()
3924 latencies = to_i915(dev)->wm.spr_latency; in spr_wm_latency_show()
3926 wm_latency_show(m, latencies); in spr_wm_latency_show()
3935 const uint16_t *latencies; in cur_wm_latency_show() local
3938 latencies = dev_priv->wm.skl_latency; in cur_wm_latency_show()
[all …]
|
| /linux-4.1.27/arch/arm/mach-shmobile/ |
| D | pm-rmobile.c | 188 struct gpd_timing_data latencies = { in rmobile_add_devices_to_domains() local
198 data[j].pdev, &latencies); in rmobile_add_devices_to_domains()
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | l2cc.txt | 37 read, write and setup latencies. Minimum valid values are 1. Controllers
40 read, write and setup latencies. Controllers without setup latency control
|
| /linux-4.1.27/Documentation/block/ |
| D | deadline-iosched.txt | 21 service time for a request. As we focus mainly on read latencies, this is
|
| D | cfq-iosched.txt | 37 throughput and acceptable latencies.
|
| D | biodoc.txt | 357 driver while servicing the request queue when it may affect latencies in
|
| /linux-4.1.27/arch/metag/mm/ |
| D | Kconfig | 46 lower latencies than main memory. This enables support for
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | emu10k1-jack.txt | 18 channels. With a post 2.6.9 Linux kernel, latencies down to 64 (1.33 ms) or
|
| /linux-4.1.27/Documentation/pps/ |
| D | pps.txt | 73 you should take into account the latencies and jitter introduced by
231 latencies. But if it is too small slave won't be able to capture clear edge
|
| /linux-4.1.27/Documentation/timers/ |
| D | NO_HZ.txt | 88 in order to avoid degrading from-idle transition latencies.
262 eliminate scheduling-clock interrupt latencies. Here are some
276 to degrade your latencies -- and that this degradation can
|
| D | highres.txt | 199 but the overall latencies have been significantly improved by this separation.
|
| /linux-4.1.27/kernel/time/ |
| D | Kconfig | 172 problems due to long sysidle latencies might wish to experiment
|
| /linux-4.1.27/arch/sh/mm/ |
| D | Kconfig | 118 the address space, each with varying latencies. This enables
|
| /linux-4.1.27/Documentation/ |
| D | pi-futex.txt | 24 determinism and well-bound latencies. Even in the worst-case, PI will
|
| /linux-4.1.27/Documentation/vm/ |
| D | page_migration | 51 process. This is necessary in order to preserve the memory latencies.
|
| /linux-4.1.27/drivers/cpufreq/ |
| D | Kconfig.x86 | 227 slowdowns and noticeable latencies. Normally Speedstep should be used
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 95 which can be used to tune the scheduler from "desktop" (i.e., low latencies) to
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 116 differentiated by varying exit latencies and power
|
| /linux-4.1.27/Documentation/trace/ |
| D | tracepoint-analysis.txt | 193 o Calculating latencies between two events
|
| D | ftrace.txt | 18 It can be used for debugging or analyzing latencies and
644 disabled and enabled respectively) that caused the latencies:
839 latencies, as described in "Latency
1881 - you are experiencing weird latencies but it's difficult to
|
| /linux-4.1.27/Documentation/power/ |
| D | pm_qos_interface.txt | 193 it may cause excess latencies to be visible to software, causing it to miss
|
| /linux-4.1.27/Documentation/RCU/ |
| D | rcubarrier.txt | 68 in realtime kernels in order to avoid excessive scheduling latencies.
|
| D | checklist.txt | 239 result in excessive realtime latencies or even OOM conditions.
|
| /linux-4.1.27/Documentation/gpio/ |
| D | consumer.txt | 183 open-drain signaling and output latencies.
|
| D | gpio-legacy.txt | 178 issues including open-drain signaling and output latencies.
|
| /linux-4.1.27/drivers/usb/gadget/ |
| D | Kconfig | 122 latencies that makes the VFS to appear bursty in a system with
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 340 that it not just introduces high allocation latencies into the
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | f2fs.txt | 71 is to hide the latencies to users. And also definitely, it should reduce the
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 670 Lower values mean lower latencies for initial faults, but at the same time
|
| /linux-4.1.27/Documentation/locking/ |
| D | rt-mutex-design.txt | 532 priority process run as long as possible with little latencies and delays.
|
| /linux-4.1.27/init/ |
| D | Kconfig | 913 # all cpu-local but of different latencies, such as SuperH.
|