Searched full:amounts (Results 1 – 25 of 141) sorted by relevance
123456
60 amounts of activity imply high activity on the zone->lock. Taking this lock65 is triggered. Significant amounts of activity here could indicate that the70 freed in batch with a page list. Significant amounts of activity here could95 consecutively imply the zone->lock being taken once. Large amounts of per-CPU98 lists should be a larger size. Finally, large amounts of refills on one CPU99 and drains on another could be a factor in causing large amounts of cache
14 NMI handlers are hogging large amounts of CPU time. The kernel
25 amounts of time (with interrupts disabled), polling the CPU Time Stamp Counter
88 unit amounts. One unit of pre-emphasis duration is approximately100 amounts. One unit amount is approximately 2 mA and is defined as
7 # and produce insane amounts of uninteresting coverage.
27 * insane amounts of padding around dev_t's.
43 * insane amounts of padding around dev_t's.
41 * insane amounts of padding around dev_t's.
8 good amounts of memory savings. Some of the usecases include /tmp storage,
53 * insane amounts of padding around dev_t's.
43 * amounts of data as those APIs may be hw-accelerated.
98 * amounts of data as those APIs may be hw-accelerated.
11 good amounts of memory savings.
50 * insane amounts of padding around dev_t's.
40 * insane amounts of padding around dev_t's.
49 problem where userspace is able to pin unrestricted amounts of memory
48 * amounts of padding around dev_t's. The memory layout is the same as of
44 when large amounts of console data are written.
71 /* Calculating by the amounts io clock and cpu clock would in init_latency_info()
52 to our runqueue. The exact number of tasks amounts to an imbalance previously
193 * Simple loop for trailing quadwords, or for small amounts371 * Simple loop for trailing quadwords, or for small amounts559 * Simple loop for trailing quadwords, or for small amounts
73 # produce more consistent amounts of data each run, to see if over
45 In the above chart minuses and slashes represent "real" data amounts, points and
86 small amounts of data amongst their nodes.
44 formats); arbitrary amounts zero bytes (for padding) can be added
