Lines Matching refs:be

18 running the command. slabinfo can be compiled with
23 be enabled on the command line. F.e. no tracking information will be
25 be performed if debugging was not switched on.
30 Parameters may be given to slub_debug. If none is specified then full
80 corresponding debug option. All options can be set on a slab that does
82 and tracing may only be enabled. The other options may cause the realignment
103 which will test all objects. Output will be generated to the syslog.
116 can be influenced by kernel parameters:
123 into one slab in order for the allocation order to be acceptable.
124 In general slub will be able to perform this number of allocations
132 longer be checked. This is useful to avoid SLUB trying to generate
183 to be booted with slub_debug) then the following output will be dumped
188 This will be a message in the system log starting with
211 	Can be useful if the corruption does not stop with the start of the
237 of the corruption is may be more likely found by looking at the function that
258 Minimal debugging (sanity checks alone) can be enabled by booting with
262 This will be generally be enough to enable the resiliency features of slub
264 keep corrupting objects. This may be important for production systems.
265 Performance will be impacted by the sanity checks and there will be a
267 will be used (unlike full debugging).
269 No guarantees. The kernel component still needs to be fixed. Performance
270 may be optimized further by locating the slab that experiences corruption
278 may be advisable to enable a Redzone to avoid corrupting the beginning