Lines Matching +full:70 +full:a

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
16 page boundaries. The code refers to these linked pages as a single entity
25 Additionally, zs_malloc() does not return a dereferenceable pointer.
31 be mapped using zs_map_object() to get a usable pointer and subsequently
38 ``/sys/kernel/debug/zsmalloc/<user name>``. Here is a sample of stat output::
42 …class  size       10%       20%       30%       40%       50%       60%       70%       80%       …
68 70%
69 	the number of zspages with usage ratio between 60% and 70%
71 	the number of zspages with usage ratio between 70% and 80%
85 	the number of 0-order pages to make a zspage
98 zsmalloc has 255 size classes, each of which can hold a number of zspages.
122 hold a total of 5 objects. If we need to store 13 objects of size 1568, we
125 However, if we take a closer look at size class #96 (which is meant for
127 find that the most optimal zspage configuration for this class is a chain
137 This means that a class #96 configuration with 5 physical pages can store 13
138 objects of size 1568 in a single zspage, using a total of 5 physical pages.
144 dewer class mergers, resulting in a more compact grouping of classes, which
147 Let's take a closer look at the bottom of `/sys/kernel/debug/zsmalloc/zramX/classes`:::
156 Size class #202 stores objects of size 3264 bytes and has a maximum of 4 pages
161 Increasing the size of the chain of zspages also results in a higher watermark
223 A synthetic test
226 zram as a build artifacts storage (Linux kernel compilation).