Lines Matching refs:slab
9 slab caches. SLUB always includes full debugging but it is off by default.
40 slub_debug=<Debug-Options>,<slab name1>,<slab name2>,...
47 of the first "select slabs" blocks that matches the slab's name are applied.
59 caused higher minimum slab orders
72 end of the slab name, in order to cover all slabs with the same prefix. For
78 Red zoning and tracking may realign the slab. We can just apply sanity checks
83 Debugging options may require the minimum possible slab order to increase as
85 sizes). This has a higher liklihood of resulting in slab allocation errors
91 You can apply different options to different list of slab names, using blocks
99 debugged by specifying global debug options followed by a list of slab names
104 The state of each debug option for a slab can be found in the respective files
107 /sys/kernel/slab/<slab name>/
120 used on the wrong slab.
140 This also works in a more limited way if boot was without slab debug.
150 governed by the order of the allocation for each slab. The allocations
159 slab in order for the allocation order to be acceptable. In
161 allocations on a slab without consulting centralized resources
172 of a slab cache with large object sizes into one high order
230 BUG <slab cache affected>: <What went wrong>
234 INFO: Slab <address> <slab information>
242 set for the slab. slub_debug sets that option)
284 FIX <slab cache affected>: <corrective action taken>
287 been overwritten. Here a string of 8 characters was written into a slab that
309 may be optimized further by locating the slab that experiences corruption