Lines Matching refs:it

28 	  and it is the best option for smaller systems.
46 	  architectures, it is considered deprecated in favor of
147 # feature. If you are not sure, don't touch it.
186 # space can be handled with less contention: split it at this NR_CPUS.
236           it and then we would be really interested to hear about that at
279 	  An architecture should select this if it implements the
295 	  mergeable.  When it finds pages of identical content, it replaces
314 	  On arm and other archs it should not be higher than 32768.
348 	  of memory on which to store mappings, but it can only ask the system
350 	  more than it requires.  To deal with this, mmap() is able to trim off
351 	  the excess and return it to the allocator.
397 	  benefit but it will work automatically for all applications.
404 	  madvise(MADV_HUGEPAGE) but it won't risk to increase the
440 	  memory.  So when the PFRA "evicts" a page, it first attempts to use
445 	  filesystem wishes to access a page in a file on disk, it first
446 	  checks cleancache to see if it already contains it; if it does,
460 	  Frontswap is so named because it can be thought of as the opposite
481 	  be allocated from it. This way, the kernel can use the memory for
519 	  soft-dirty bit on pte-s. This bit it set when someone writes
521 	  it can be cleared by hands.
538 	  This is marked experimental because it is a new feature (as of
555 	  page.  While this design limits storage density, it has simple and
556 	  deterministic reclaim properties that make it preferable to a higher
722 	  This is marked experimental because it is a new feature. Write
733 # introduced it on powerpc.  This allows for a more flexible hugepage