diff options
| author |  Waiman Long <longman@redhat.com>
| 2017-01-05 15:17:04 -0500 |
|---|---|---|
| committer |  Thomas Gleixner <tglx@linutronix.de>
| 2017-02-04 09:01:55 +0100 |
| commit | 97dd552eb23c83dbf626a6e84666c7e281375d47 (patch) | |
| tree | a9a5358b76f201f915051d42ea5e1358a93ab9c0 /include/crypto | |
| parent | debugobjects: Track number of kmem_cache_alloc/kmem_cache_free done (diff) | |
| download | linux-97dd552eb23c83dbf626a6e84666c7e281375d47.tar.gz linux-97dd552eb23c83dbf626a6e84666c7e281375d47.tar.bz2 linux-97dd552eb23c83dbf626a6e84666c7e281375d47.zip | |
debugobjects: Scale thresholds with # of CPUs
On a large SMP systems with hundreds of CPUs, the current thresholds
for allocating and freeing debug objects (256 and 1024 respectively)
may not work well. This can cause a lot of needless calls to
kmem_aloc() and kmem_free() on those systems.
To alleviate this thrashing problem, the object freeing threshold
is now increased to "1024 + # of CPUs * 32". Whereas the object
allocation threshold is increased to "256 + # of CPUs * 4". That
should make the debug objects subsystem scale better with the number
of CPUs available in the system.
Signed-off-by: Waiman Long <longman@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Du Changbin" <changbin.du@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Stancek <jstancek@redhat.com>
Link: http://lkml.kernel.org/r/1483647425-4135-3-git-send-email-longman@redhat.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'include/crypto')
0 files changed, 0 insertions, 0 deletions