Searched full:amounts (Results 1 – 25 of 261) sorted by relevance
1234567891011
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
94 unit amounts. One unit of pre-emphasis duration is approximately106 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.
8 good amounts of memory savings. Some of the usecases include /tmp storage,
41 * insane amounts of padding around dev_t's.
10 good amounts of memory savings.
53 * insane amounts of padding around dev_t's.
43 * amounts of data as those APIs may be hw-accelerated.
50 * insane amounts of padding around dev_t's.
56 * amounts to the whole of vmlinux with LTO enabled), Clang will drop the
11 good amounts of memory savings.
48 * amounts of padding around dev_t's. The memory layout is the same as of
40 * insane amounts of padding around dev_t's.