Lines Matching refs:of
10 any object of size PAGE_SIZE/2 or larger would occupy an entire page.
11 This was one of the major issues with its predecessor (xvmalloc).
13 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
19 For simplicity, zsmalloc can only allocate objects of size up to PAGE_SIZE
20 since this satisfies the requirements of all its current users (in the
27 location of the allocated object. The reason for this indirection is that
38 ``/sys/kernel/debug/zsmalloc/<user name>``. Here is a sample of stat output::
58 the number of ZS_ALMOST_EMPTY zspages(see below)
60 the number of ZS_ALMOST_FULL zspages(see below)
62 the number of objects allocated
64 the number of objects allocated to the user
66 the number of pages allocated for the class
68 the number of 0-order pages to make a zspage
72 * n = number of allocated objects
73 * N = total number of objects zspage can store
86 zsmalloc has 255 size classes, each of which can hold a number of zspages.
89 creation of the zsmalloc pool (see calculate_zspage_chain_size()).
92 characteristics in terms of the number of pages per zspage and the number
93 of objects that each zspage can store.
105 need to store an object of size, say, 1568 bytes, we end up using size class
106 #100 instead of size class #96. Size class #100 is meant for objects of size
107 1632 bytes, so each object of size 1568 bytes wastes 1632-1568=64 bytes.
109 Size class #100 consists of zspages with 2 physical pages each, which can
110 hold a total of 5 objects. If we need to store 13 objects of size 1568, we
114 objects of size 1568 bytes) and trace `calculate_zspage_chain_size()`, we
116 of 5 physical pages:::
126 objects of size 1568 in a single zspage, using a total of 5 physical pages.
128 physical pages to store the same number of objects.
132 dewer class mergers, resulting in a more compact grouping of classes, which
135 Let's take a closer look at the bottom of `/sys/kernel/debug/zsmalloc/zramX/classes`:::
143 Size class #202 stores objects of size 3264 bytes and has a maximum of 4 pages
148 Increasing the size of the chain of zspages also results in a higher watermark
150 efficient storage of large objects.
152 For zspage chain size of 8, huge class watermark becomes 3632 bytes:::
164 For zspage chain size of 16, huge class watermark becomes 3840 bytes:::
192 pages per zspage number of size classes (clusters) huge size class watermark
239 in the example where the number of physical pages used decreased from 159955
247 the limit on the size of the zspage chains (as specified by the