Lines Matching +full:higher +full:- +full:end

7 never attempts higher order page allocation which is very likely to
9 (0-order) pages, it would suffer from very high fragmentation --
13 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
15 pages act as a single higher-order page i.e. an object can span 0-order
21 worst case, page is incompressible and is thus stored "as-is" i.e. in
29 issues on 32-bit systems where the VA region for kernel space mappings
85 	the number of 0-order pages to make a zspage
99 Each zspage can contain up to ZSMALLOC_CHAIN_SIZE physical (0-order) pages.
116 Size classes #95-99 are merged with size class #100. This means that when we
117 need to store an object of size, say, 1568 bytes, we end up using size class
119 1632 bytes, so each object of size 1568 bytes wastes 1632-1568=64 bytes.
123 end up allocating three zspages, or 6 physical pages.
143 such as pages per-zspage and objects per-zspage also change. This leads to
161 Increasing the size of the chain of zspages also results in a higher watermark
224 ----------------
270 .. kernel-doc:: mm/zsmalloc.c