Lines Matching refs:zspage

17 called zspage.
55 	object size zspage stores
85 	the number of 0-order pages to make a zspage
89 Each zspage maintains inuse counter which keeps track of the number of
90 objects stored in the zspage.  The inuse counter determines the zspage's
92 the total number of objects the zspage can hold (objs_per_zspage). The
99 Each zspage can contain up to ZSMALLOC_CHAIN_SIZE physical (0-order) pages.
100 The optimal zspage chain size for each size class is calculated during the
104 characteristics in terms of the number of pages per zspage and the number
105 of objects that each zspage can store.
127 find that the most optimal zspage configuration for this class is a chain
130     pages per zspage      wasted bytes     used%
138 objects of size 1568 in a single zspage, using a total of 5 physical pages.
142 As the zspage chain size for class #96 increases, its key characteristics
143 such as pages per-zspage and objects per-zspage also change. This leads to
157 per zspage. Any object larger than 3264 bytes is considered huge and belongs
165 For zspage chain size of 8, huge class watermark becomes 3632 bytes:::
178 For zspage chain size of 16, huge class watermark becomes 3840 bytes:::
205 Overall the combined zspage chain size effect on zsmalloc pool configuration:::
207   pages per zspage   number of size classes (clusters)   huge size class watermark
255 Using larger zspage chains may result in using fewer physical pages, as seen
264 the limit on the size of the zspage chains (as specified by the