Home
last modified time | relevance | path

Searched full:jitter (Results 1 – 25 of 133) sorted by relevance

123456

/linux/Documentation/admin-guide/
H A Dkernel-per-CPU-kthreads.rst2 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/Documentation/timers/
H A Dno_hz.rst8 efficiency and reducing OS jitter. Reducing OS jitter is important for
202 So you enable all the OS-jitter features described in this document,
204 your workload isn't affected that much by OS jitter, or is it because
206 by providing a simple OS-jitter test suite, which is available on branch
213 whether or not you have succeeded in removing OS jitter from your system.
214 If this trace shows that you have removed OS jitter as much as is
216 sensitive to OS jitter.
219 We do not currently have a good way to remove OS jitter from single-CPU
286 of OS jitter, including interrupts and system-utility tasks
290 * Some sources of OS jitter can currently be eliminated only by
[all …]
/linux/tools/testing/selftests/rcutorture/bin/
H A Djitterstart.sh4 # 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" "$@" &
H A Dkvm.sh57 jitter="-1"
78 echo " --jitter N [ maxsleep (us) [ maxspin (us) ] ]"
187 --jitter)
188 …checkarg --jitter "(# threads [ sleep [ spin ] ])" $# "$2" '^-\{,1\}[0-9]\+\( \+[0-9]\+\)\{,2\} *$…
189 jitter="$2"
256 # If you really want jitter for refscale or
258 # or the refscale. (But why jitter in these cases?)
259 jitter=0
472 split(jitter, ja);
532 print "echo Build-only run, so suppressing jitter | tee -a " rd "log"
[all …]
H A Djitter.sh5 # of this script is to inflict random OS jitter on a concurrently running
8 # Usage: jitter.sh me jittering-path duration [ sleepmax [ spinmax ] ]
H A Dkvm-test-1-run-batch.sh48 # Start up jitter, start each scenario, wait, end jitter.
H A Dkvm-transform.sh10 # jitter_dir: Jitter directory for TORTURE_JITTER_START and
42 echo "Need valid jitter directory: '$jitter_dir'"
H A Djitterstop.sh4 # Remove the "jittering" file, signaling the jitter.sh scripts to stop,
/linux/crypto/
H A Djitterentropy.c2 * 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…
247 * The Jitter RNG uses an enhanced version of the Repetition Count Test
250 * values during the generation of one Jitter RNG output block.
254 * During the counting operation, the Jitter RNG always calculates the RCT
256 * the Jitter RNG output block will be calculated completely but discarded at
257 * the end. The caller of the Jitter RNG is informed with an error code.
309 * 1st derivative of the jitter measurement (time delta)
310 * 2nd derivative of the jitter measurement (delta of time deltas)
[all …]
H A DKconfig1246 tristate "CPU Jitter Non-Deterministic RNG (Random Number Generator)"
1250 CPU Jitter RNG (Random Number Generator) from the Jitterentropy library
1264 prompt "CPU Jitter RNG Memory Size"
1267 The Jitter RNG measures the execution time of memory accesses.
1276 the entropy rate produced by the Jitter RNG can be modified.
1306 int "CPU Jitter RNG Oversampling Rate"
1310 The Jitter RNG allows the specification of an oversampling rate (OSR).
1311 The Jitter RNG operation requires a fixed amount of timing
1315 by the OSR factor. The oversampling allows the Jitter RNG to operate
1318 trade-off, however, is that the Jitter RNG now requires more time
[all …]
H A Djitterentropy-kcapi.c2 * Non-physical true random number generator based on timing jitter --
235 * Jitter RNG's unpredictable behavior. If we have a slower hash in jent_kcapi_init()
294 panic("Jitter RNG permanent health test failure\n"); in jent_kcapi_random()
296 pr_err("Jitter RNG permanent health test failure\n"); in jent_kcapi_random()
300 pr_warn_ratelimited("Reset Jitter RNG due to intermittent health test failure\n"); in jent_kcapi_random()
375 MODULE_DESCRIPTION("Non-physical True Random Number Generator based on CPU Jitter");
/linux/kernel/time/
H A Dntp.c106 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()
883 /* get current phase correction and jitter */
884 static inline long pps_phase_filter_get(long *jitter) in pps_phase_filter_get() argument
886 *jitter = pps_tf[0] - pps_tf[1]; in pps_phase_filter_get()
887 if (*jitter < 0) in pps_phase_filter_get()
[all …]
/linux/include/uapi/linux/
H A Dtimex.h81 __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/include/linux/usb/
H A Dmidi-v2.h41 #define USB_MS_MIDI_PROTO_1_0_64_JRTS 0x02 /* MIDI 1.0, UMP up to 64bits, Jitter Reduction Timestam…
43 #define USB_MS_MIDI_PROTO_1_0_128_JRTS 0x04 /* MIDI 1.0, UMP up to 128bits, Jitter Reduction Timest…
45 #define USB_MS_MIDI_PROTO_2_0_JRTS 0x12 /* MIDI 2.0, Jitter Reduction Timestamps */
/linux/net/sched/
H A Dsch_netem.c43 packets and add random jitter (and correlation). The random
77 /* a linear queue; reduces rbtree rebalancing when jitter is low */
87 s64 jitter; member
477 if (q->latency || q->jitter || q->rate) in netem_enqueue()
553 delay = tabledist(q->latency, q->jitter, in netem_enqueue()
1018 q->jitter = PSCHED_TICKS2NS(qopt->jitter); in netem_change()
1051 q->jitter = nla_get_s64(tb[TCA_NETEM_JITTER64]); in netem_change()
1059 /* capping jitter to the range acceptable by tabledist() */ in netem_change()
1060 q->jitter = min_t(s64, abs(q->jitter), INT_MAX); in netem_change()
1169 qopt.jitter = min_t(psched_time_t, PSCHED_NS2TICKS(q->jitter), in netem_dump()
[all …]
/linux/include/net/
H A Dieee8021q.h17 * @IEEE8021Q_TT_VI: Video, < 100 ms latency and jitter
18 * @IEEE8021Q_TT_VO: Voice, < 10 ms latency and jitter
/linux/Documentation/sound/cards/
H A Dimg-spdif-in.rst43 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/drivers/iio/frequency/
H A DKconfig15 tristate "Analog Devices AD9523 Low Jitter Clock Generator"
18 Say yes here to build support for Analog Devices AD9523 Low Jitter
/linux/drivers/media/pci/mantis/
H A Dmantis_pcmcia.c28 * again, definitely it is jitter alone
52 * again, definitely it is jitter alone
/linux/kernel/trace/
H A Dtrace_clock.c11 * - medium: scalable global clock with some jitter
54 * jitter between CPUs. So it's a pretty scalable clock, but there
/linux/kernel/rcu/
H A DKconfig244 Use this option to reduce OS jitter for aggressive HPC or
247 asymmetric multiprocessors. The price of this reduced jitter
263 Say Y here if you need reduced OS jitter, despite added overhead.
/linux/drivers/input/touchscreen/
H A Dmk712.c21 * 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/drivers/clk/
H A DKconfig54 tristate "Ti LMK04832 JESD204B Compliant Clock Jitter Cleaner"
59 Low-Noise JESD204B Compliant Clock Jitter Cleaner With Dual Loop PLLs
423 and jitter attenuator ICs with fractional and integer dividers.
H A Dclk-max77686.c258 /* 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/include/linux/
H A Dtrace_clock.h10 * - medium: scalable global clock with some jitter

123456