| .. | .. |
|---|
| 346 | 346 | number of objects per slab. If a slab cannot be allocated |
|---|
| 347 | 347 | because of fragmentation, SLUB will retry with the minimum order |
|---|
| 348 | 348 | possible depending on its characteristics. |
|---|
| 349 | + |
|---|
| 349 | 350 | When debug_guardpage_minorder=N (N > 0) parameter is specified |
|---|
| 350 | 351 | (see Documentation/admin-guide/kernel-parameters.rst), the minimum possible |
|---|
| 351 | 352 | order is used and this sysfs entry can not be used to change |
|---|
| .. | .. |
|---|
| 361 | 362 | new slab has not been possible at the cache's order and instead |
|---|
| 362 | 363 | fallen back to its minimum possible order. It can be written to |
|---|
| 363 | 364 | clear the current count. |
|---|
| 365 | + |
|---|
| 364 | 366 | Available when CONFIG_SLUB_STATS is enabled. |
|---|
| 365 | 367 | |
|---|
| 366 | 368 | What: /sys/kernel/slab/cache/partial |
|---|
| .. | .. |
|---|
| 410 | 412 | slab from a remote node as opposed to allocating a new slab on |
|---|
| 411 | 413 | the local node. This reduces the amount of wasted memory over |
|---|
| 412 | 414 | the entire system but can be expensive. |
|---|
| 415 | + |
|---|
| 413 | 416 | Available when CONFIG_NUMA is enabled. |
|---|
| 414 | 417 | |
|---|
| 415 | 418 | What: /sys/kernel/slab/cache/sanity_checks |
|---|
| .. | .. |
|---|
| 429 | 432 | Contact: Pekka Enberg <penberg@cs.helsinki.fi>, |
|---|
| 430 | 433 | Christoph Lameter <cl@linux-foundation.org> |
|---|
| 431 | 434 | Description: |
|---|
| 432 | | - The shrink file is written when memory should be reclaimed from |
|---|
| 433 | | - a cache. Empty partial slabs are freed and the partial list is |
|---|
| 434 | | - sorted so the slabs with the fewest available objects are used |
|---|
| 435 | | - first. |
|---|
| 435 | + The shrink file is used to reclaim unused slab cache |
|---|
| 436 | + memory from a cache. Empty per-cpu or partial slabs |
|---|
| 437 | + are freed and the partial list is sorted so the slabs |
|---|
| 438 | + with the fewest available objects are used first. |
|---|
| 439 | + It only accepts a value of "1" on write for shrinking |
|---|
| 440 | + the cache. Other input values are considered invalid. |
|---|
| 441 | + Shrinking slab caches might be expensive and can |
|---|
| 442 | + adversely impact other running applications. So it |
|---|
| 443 | + should be used with care. |
|---|
| 436 | 444 | |
|---|
| 437 | 445 | What: /sys/kernel/slab/cache/slab_size |
|---|
| 438 | 446 | Date: May 2007 |
|---|