/Linux-v6.1/Documentation/admin-guide/ |
D | kernel-per-CPU-kthreads.rst | 2 Reducing OS jitter due to per-cpu kthreads 6 options to control their OS jitter. Note that non-per-CPU kthreads are 7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind 26 - In order to locate kernel-generated OS jitter on CPU N: 43 To reduce its OS jitter, do any of the following: 62 To reduce its OS jitter, do the following: 73 To reduce its OS jitter, do one of the following: 87 To reduce its OS jitter, each softirq vector must be handled 202 housekeeping CPUs, which can tolerate OS jitter. 228 To reduce its OS jitter, do any of the following: [all …]
|
/Linux-v6.1/tools/testing/selftests/rcutorture/bin/ |
D | jitterstart.sh | 4 # Start up the specified number of jitter.sh scripts in the background. 8 # n: Number of jitter.sh scripts to start up. 21 echo jitterstart.sh: Missing count of jitter.sh scripts to start. 36 jitter.sh $jitter_i "${jittering_dir}/jittering" "$@" &
|
D | kvm.sh | 57 jitter="-1" 77 echo " --jitter N [ maxsleep (us) [ maxspin (us) ] ]" 177 --jitter) 178 …checkarg --jitter "(# threads [ sleep [ spin ] ])" $# "$2" '^-\{,1\}[0-9]\+\( \+[0-9]\+\)\{,2\} *$… 179 jitter="$2" 246 # If you really want jitter for refscale or 248 # or the refscale. (But why jitter in these cases?) 249 jitter=0 462 split(jitter, ja); 522 print "echo Build-only run, so suppressing jitter | tee -a " rd "log" [all …]
|
D | jitter.sh | 5 # of this script is to inflict random OS jitter on a concurrently running 8 # Usage: jitter.sh me jittering-path duration [ sleepmax [ spinmax ] ]
|
D | kvm-test-1-run-batch.sh | 49 # Start up jitter, start each scenario, wait, end jitter.
|
D | jitterstop.sh | 4 # Remove the "jittering" file, signaling the jitter.sh scripts to stop,
|
/Linux-v6.1/drivers/staging/greybus/tools/ |
D | README.loopback | 180 requests per-sec: min=390, max=547, average=469.299988, jitter=157 181 ap-throughput B/s: min=90480 max=126904 average=108762.101562 jitter=36424 182 ap-latency usec: min=1826 max=2560 average=2146.000000 jitter=734 183 apbridge-latency usec: min=1620 max=1982 average=1882.099976 jitter=362 184 gpbridge-latency usec: min=56 max=57 average=57.099998 jitter=1 194 requests per-sec: min=397, max=538, average=461.700012, jitter=141 195 ap-throughput B/s: min=92104 max=124816 average=106998.898438 jitter=32712 196 ap-latency usec: min=1856 max=2514 average=2185.699951 jitter=658 197 apbridge-latency usec: min=1460 max=2296 average=1828.599976 jitter=836 198 gpbridge-latency usec: min=56 max=57 average=57.099998 jitter=1
|
/Linux-v6.1/crypto/ |
D | jitterentropy.c | 2 * Non-physical true random number generator based on timing jitter -- 3 * Jitter RNG standalone code. 54 …#error "The CPU Jitter random number generator must not be compiled with optimizations. See docume… 188 * The Jitter RNG uses an enhanced version of the Repetition Count Test 191 * values during the generation of one Jitter RNG output block. 195 * During the counting operation, the Jitter RNG always calculates the RCT 197 * the Jitter RNG output block will be calculated completely but discarded at 198 * the end. The caller of the Jitter RNG is informed with an error code. 267 * 1st derivative of the jitter measurement (time delta) 268 * 2nd derivative of the jitter measurement (delta of time deltas) [all …]
|
D | jitterentropy-kcapi.c | 2 * Non-physical true random number generator based on timing jitter -- 151 pr_warn_ratelimited("Reset Jitter RNG due to health test failure: %s failure\n", in jent_kcapi_random() 161 /* Convert the Jitter RNG error into a usable error code */ in jent_kcapi_random() 216 MODULE_DESCRIPTION("Non-physical True Random Number Generator based on CPU Jitter");
|
/Linux-v6.1/Documentation/timers/ |
D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for 205 So you enable all the OS-jitter features described in this document, 207 your workload isn't affected that much by OS jitter, or is it because 209 by providing a simple OS-jitter test suite, which is available on branch 216 whether or not you have succeeded in removing OS jitter from your system. 217 If this trace shows that you have removed OS jitter as much as is 219 sensitive to OS jitter. 222 We do not currently have a good way to remove OS jitter from single-CPU 289 of OS jitter, including interrupts and system-utility tasks 293 * Some sources of OS jitter can currently be eliminated only by [all …]
|
/Linux-v6.1/kernel/time/ |
D | ntp.c | 106 static long pps_jitter; /* current jitter (ns) */ 117 static long pps_jitcnt; /* jitter limit exceeded */ 182 /* PPS jitter exceeded when in is_error_status() 197 txc->jitter = pps_jitter; in pps_fill_timex() 199 txc->jitter = pps_jitter / NSEC_PER_USEC; in pps_fill_timex() 229 txc->jitter = 0; in pps_fill_timex() 876 /* get current phase correction and jitter */ 877 static inline long pps_phase_filter_get(long *jitter) in pps_phase_filter_get() argument 879 *jitter = pps_tf[0] - pps_tf[1]; in pps_phase_filter_get() 880 if (*jitter < 0) in pps_phase_filter_get() [all …]
|
/Linux-v6.1/include/uapi/linux/ |
D | timex.h | 81 __kernel_long_t jitter; /* pps jitter (us) (ro) */ member 84 __kernel_long_t jitcnt; /* jitter limit exceeded (ro) */ 120 long long jitter; /* pps jitter (us) (ro) */ member 124 long long jitcnt; /* jitter limit exceeded (ro) */ 182 #define STA_PPSJITTER 0x0200 /* PPS signal jitter exceeded (ro) */
|
/Linux-v6.1/net/sched/ |
D | sch_netem.c | 42 packets and add random jitter (and correlation). The random 76 /* a linear queue; reduces rbtree rebalancing when jitter is low */ 86 s64 jitter; member 470 if (q->latency || q->jitter || q->rate) in netem_enqueue() 536 delay = tabledist(q->latency, q->jitter, in netem_enqueue() 1000 q->jitter = PSCHED_TICKS2NS(qopt->jitter); in netem_change() 1033 q->jitter = nla_get_s64(tb[TCA_NETEM_JITTER64]); in netem_change() 1041 /* capping jitter to the range acceptable by tabledist() */ in netem_change() 1042 q->jitter = min_t(s64, abs(q->jitter), INT_MAX); in netem_change() 1148 qopt.jitter = min_t(psched_time_t, PSCHED_NS2TICKS(q->jitter), in netem_dump() [all …]
|
/Linux-v6.1/Documentation/sound/cards/ |
D | img-spdif-in.rst | 43 This control is used to modify the locking/jitter rejection characteristics 44 of the block. Larger values increase the locking range, but reduce jitter
|
/Linux-v6.1/drivers/iio/frequency/ |
D | Kconfig | 15 tristate "Analog Devices AD9523 Low Jitter Clock Generator" 18 Say yes here to build support for Analog Devices AD9523 Low Jitter
|
/Linux-v6.1/drivers/media/pci/mantis/ |
D | mantis_pcmcia.c | 28 * again, definitely it is jitter alone 52 * again, definitely it is jitter alone
|
/Linux-v6.1/kernel/rcu/ |
D | Kconfig | 245 Use this option to reduce OS jitter for aggressive HPC or 248 asymmetric multiprocessors. The price of this reduced jitter 264 Say Y here if you need reduced OS jitter, despite added overhead.
|
/Linux-v6.1/kernel/trace/ |
D | trace_clock.c | 11 * - medium: scalable global clock with some jitter 54 * jitter between CPUs. So it's a pretty scalable clock, but there
|
/Linux-v6.1/drivers/input/touchscreen/ |
D | mk712.c | 21 * 1999-12-19: added anti-jitter code, report pen-up events, fixed mk712_poll 24 * 2000-01-05: checked in new anti-jitter code, changed mouse protocol, fixed
|
/Linux-v6.1/include/linux/ |
D | trace_clock.h | 10 * - medium: scalable global clock with some jitter
|
D | mISDNdsp.h | 35 int unclocked; /* data is not clocked (has jitter/loss) */
|
/Linux-v6.1/drivers/clk/ |
D | Kconfig | 55 tristate "Ti LMK04832 JESD204B Compliant Clock Jitter Cleaner" 60 Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs 387 and jitter attenuator ICs with fractional and integer dividers.
|
D | clk-max77686.c | 258 /* MAX77802: Enable low-jitter mode on the 32khz clocks. */ in max77686_clk_probe() 264 dev_err(dev, "Failed to config low-jitter: %d\n", ret); in max77686_clk_probe()
|
/Linux-v6.1/drivers/hte/ |
D | Kconfig | 10 less jitter. This framework provides a generic interface to such HTE
|
/Linux-v6.1/arch/ia64/kernel/ |
D | time.c | 252 printk("Jitter checking for ITC timers disabled\n"); in nojitter_setup() 324 * Jitter compensation requires a cmpxchg which may limit in ia64_init_itm() 343 * Note that jitter compensation is off! There is no point of in ia64_init_itm()
|