Lines Matching refs:may
77 root may not be able to log in to recover the system.
126 one of them may be specified at a time. When one sysctl is written it is
147 Note: dirty_bytes is the counterpart of dirty_ratio. Only one of them may be
201 To increase the number of objects freed by this operation, the user may run
211 objects, it may cost a significant amount of I/O and CPU to recreate the
215 You may see informational messages in your kernel log when this file is
374 may have. Memory map areas are used as a side-effect of calling
379 programs, particularly malloc debuggers, may consume lots of them,
454 and may not be fast.
527 you may be able to read ZONE_DMA as ZONE_DMA32...)
577 large systems with thousands of tasks it may not be feasible to dump
580 information may not be desired.
616 of them may be specified at a time. Setting one disables the other (which
666 The default value is three (eight pages at a time). There may be some
687 may be killed by oom-killer. No panic occurs in this case.
688 Because other nodes' memory may be free. This means system total status
689 may be not fatal yet.
772 Increasing vfs_cache_pressure significantly beyond 100 may have negative
797 zone_reclaim may be enabled if it's known that the workload is partitioned
806 throttle the process. This may decrease the performance of a single process