Lines Matching refs:objects

19 For simplicity, zsmalloc can only allocate objects of size up to PAGE_SIZE
79 	the number of objects allocated
81 	the number of objects allocated to the user
90 objects stored in the zspage.  The inuse counter determines the zspage's
91 "fullness group" which is calculated as the ratio of the "inuse" objects to
92 the total number of objects the zspage can hold (objs_per_zspage). The
105 of objects that each zspage can store.
118 #100 instead of size class #96. Size class #100 is meant for objects of size
122 hold a total of 5 objects. If we need to store 13 objects of size 1568, we
126 objects of size 1568 bytes) and trace `calculate_zspage_chain_size()`, we
138 objects of size 1568 in a single zspage, using a total of 5 physical pages.
140 physical pages to store the same number of objects.
143 such as pages per-zspage and objects per-zspage also change. This leads to
156 Size class #202 stores objects of size 3264 bytes and has a maximum of 4 pages
158 to size class #254, which stores each object in its own physical page (objects
163 efficient storage of large objects.
263 objects and release zspages. In these cases, it is recommended to decrease