/freebsd/sys/cam/ |
H A D | cam_iosched.c | 282 uint64_t latencies[LAT_BUCKETS]; member 977 uint64_t *latencies; in cam_iosched_sysctl_latencies() local 979 latencies = arg1; in cam_iosched_sysctl_latencies() 983 sbuf_printf(&sb, "%jd,", (intmax_t)latencies[i]); in cam_iosched_sysctl_latencies() 984 sbuf_printf(&sb, "%jd", (intmax_t)latencies[LAT_BUCKETS - 1]); in cam_iosched_sysctl_latencies() 1088 &ios->latencies, 0, in cam_iosched_iop_stats_sysctl_init() 1911 static sbintime_t latencies[LAT_BUCKETS - 1] = { variable 1980 if (sim_latency < latencies[i]) { in cam_iosched_update() 1981 iop->latencies[i]++; in cam_iosched_update() 1986 iop->latencies[i]++; /* Put all > 8192ms values into the last bucket. */ in cam_iosched_update()
|
/freebsd/contrib/llvm-project/llvm/lib/Target/PowerPC/ |
H A D | P9InstrResources.td | 815 // operations cannot be done at the same time and so their latencies are added. 827 // operations cannot be done at the same time and so their latencies are added. 837 // operations cannot be done at the same time and so their latencies are added. 848 // their latencies are added. 860 // operations cannot be done at the same time and so their latencies are added. 880 // Since the Load and the PM cannot be done at the same time the latencies are 1025 // latencies are not added together. Otherwise this is like having two 1037 // latencies are not added together. Otherwise this is like having two 1063 // latencies are not added together. Otherwise this is like having two 1074 // latencies are not added together. Otherwise this is like having two [all …]
|
H A D | PPCScheduleP9.td | 384 // 2 or 5 cycle latencies for the branch unit. 402 // so the latencies for their resources must be added.
|
/freebsd/sys/contrib/device-tree/Bindings/powerpc/opal/ |
H A D | power-mgt.txt | 60 - ibm,cpu-idle-state-latencies-ns: 62 exit-latencies (in ns) for the idle states in
|
/freebsd/contrib/llvm-project/llvm/lib/Target/ARM/ |
H A D | ARMScheduleM4.td | 35 // Some definitions of latencies we apply to different instructions
|
H A D | ARMScheduleM55.td | 47 // For this schedule, we currently model latencies and pipelines well for each 73 // one). These use normal resources and latencies, but set SingleIssue = 0.
|
H A D | ARMSchedule.td | 38 // shorter latencies to certain registers as needed in the example above.
|
H A D | ARMScheduleA9.td | 1975 // NEON has an odd mix of latencies. Simply name the write types by latency. 2310 // latencies here. WAW latencies are sometimes longer. 2369 // has a def operand so the WriteL latencies are unused.
|
H A D | ARMFeatures.td | 337 // extra cycle. Take that into account when computing operand latencies.
|
/freebsd/contrib/llvm-project/llvm/lib/Target/AArch64/ |
H A D | AArch64SchedA53.td | 59 // shift-only instruction. These latencies will be incorrect when the 98 // accounted for in the WriteST* latencies below
|
H A D | AArch64SchedA55.td | 63 // These latencies are modeled without taking into account forwarding paths 64 // (the software optimisation guide lists latencies taking into account
|
H A D | AArch64SchedThunderX.td | 47 // latencies.
|
H A D | AArch64SchedA510.td | 22 // Most loads have a latency of 2, but some have higher latencies. 65 // These latencies are modeled without taking into account forwarding paths 66 // (the software optimisation guide lists latencies taking into account
|
H A D | AArch64SchedAmpere1.td | 583 // Map the target-defined scheduler read/write resources and latencies for Ampere-1.
|
H A D | AArch64SchedAmpere1B.td | 539 // Map the target-defined scheduler read/write resources and latencies for Ampere-1.
|
H A D | AArch64SchedOryon.td | 512 // On VXU doc, p37 -- latencies and throughput
|
/freebsd/contrib/libpcap/doc/ |
H A D | README.dag | 47 filtering) for efficiency. This can introduce high latencies on quiet
|
/freebsd/contrib/llvm-project/llvm/lib/Target/X86/ |
H A D | X86Schedule.td | 732 // latencies. Since these latencies are not used for pipeline hazards,
|
H A D | X86ScheduleBtVer2.td | 425 // instruction latency is set to the MAX of all the write latencies. That's why
|
/freebsd/crypto/openssl/crypto/ |
H A D | sparccpuid.S | 263 ! (*) result has lesser to do with VIS instruction latencies, rdtick
|
/freebsd/contrib/llvm-project/llvm/include/llvm/Target/ |
H A D | Target.td | 707 // This instruction is not expected to be queried for scheduling latencies
|
/freebsd/contrib/ntp/ntpd/ |
H A D | invoke-ntp.conf.texi | 2266 latencies, different cable lengths or receiver internal delay.
|
H A D | ntp.conf.def | 2378 latencies, different cable lengths or receiver internal delay.
|
/freebsd/sys/contrib/dev/acpica/ |
H A D | changes.txt | 18022 Fixed checks on C2/C3 latencies to be inclusive of maximum values.
|
/freebsd/contrib/one-true-awk/testdir/ |
H A D | funstack.in | 6092 annote = "Analysis, design of hardware. Minimizing seeks and latencies.",
|