spl-module-parameters.5: remove spl_kmem_cache_{expire,obj_per_slab_min}
Both were removed in 4fbdb10c7b
("remove
kmem_cache module parameter KMC_EXPIRE_AGE")
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Richard Laager <rlaager@wiktel.com>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Closes #12157
This commit is contained in:
parent
6e01b47a28
commit
2fe8060cee
|
@ -14,33 +14,6 @@ Description of the different parameters to the SPL module.
|
|||
.sp
|
||||
.LP
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBspl_kmem_cache_expire\fR (uint)
|
||||
.ad
|
||||
.RS 12n
|
||||
Cache expiration is part of default Illumos cache behavior. The idea is
|
||||
that objects in magazines which have not been recently accessed should be
|
||||
returned to the slabs periodically. This is known as cache aging and
|
||||
when enabled objects will be typically returned after 15 seconds.
|
||||
.sp
|
||||
On the other hand Linux slabs are designed to never move objects back to
|
||||
the slabs unless there is memory pressure. This is possible because under
|
||||
Linux the cache will be notified when memory is low and objects can be
|
||||
released.
|
||||
.sp
|
||||
By default only the Linux method is enabled. It has been shown to improve
|
||||
responsiveness on low memory systems and not negatively impact the performance
|
||||
of systems with more memory. This policy may be changed by setting the
|
||||
\fBspl_kmem_cache_expire\fR bit mask as follows, both policies may be enabled
|
||||
concurrently.
|
||||
.sp
|
||||
0x01 - Aging (Illumos), 0x02 - Low memory (Linux)
|
||||
.sp
|
||||
Default value: \fB0x02\fR
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
|
@ -85,20 +58,6 @@ take longer.
|
|||
Default value: \fB8\fR
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
\fBspl_kmem_cache_obj_per_slab_min\fR (uint)
|
||||
.ad
|
||||
.RS 12n
|
||||
The minimum number of objects allowed per slab. Normally slabs will contain
|
||||
\fBspl_kmem_cache_obj_per_slab\fR objects but for caches that contain very
|
||||
large objects it's desirable to only have a few, or even just one, object per
|
||||
slab.
|
||||
.sp
|
||||
Default value: \fB1\fR
|
||||
.RE
|
||||
|
||||
.sp
|
||||
.ne 2
|
||||
.na
|
||||
|
|
|
@ -527,9 +527,7 @@ spl_cache_flush(spl_kmem_cache_t *skc, spl_kmem_magazine_t *skm, int flush)
|
|||
* Size a slab based on the size of each aligned object plus spl_kmem_obj_t.
|
||||
* When on-slab we want to target spl_kmem_cache_obj_per_slab. However,
|
||||
* for very small objects we may end up with more than this so as not
|
||||
* to waste space in the minimal allocation of a single page. Also for
|
||||
* very large objects we may use as few as spl_kmem_cache_obj_per_slab_min,
|
||||
* lower than this and we will fail.
|
||||
* to waste space in the minimal allocation of a single page.
|
||||
*/
|
||||
static int
|
||||
spl_slab_size(spl_kmem_cache_t *skc, uint32_t *objs, uint32_t *size)
|
||||
|
|
Loading…
Reference in New Issue