aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorItaru Kitayama <i-kitayama@ap.jp.nec.com>2008-03-05 15:07:30 -0800
committerChristoph Lameter <clameter@sgi.com>2008-03-06 16:21:50 -0800
commit989a7241df87526bfef0396567e71ebe53a84ae4 (patch)
tree7e11acf87a8a8be7cf515aaed16a762aa025fc9b /Documentation
parent6d2144d355d2a532e5cc3fc12a6ba2a8d4ef15e4 (diff)
downloadlinux-989a7241df87526bfef0396567e71ebe53a84ae4.tar.gz
slub: fix typo in Documentation/vm/slub.txt
slub_debug=,dentry is correct, not dentry_cache. Signed-off-by: Itaru Kitayama <i-kitayama@ap.jp.nec.com> Signed-off-by: Christoph Lameter <clameter@sgi.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/vm/slub.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/vm/slub.txt b/Documentation/vm/slub.txt
index dcf8bcf846d..7c13f22a0c9 100644
--- a/Documentation/vm/slub.txt
+++ b/Documentation/vm/slub.txt
@@ -50,14 +50,14 @@ F.e. in order to boot just with sanity checks and red zoning one would specify:
Trying to find an issue in the dentry cache? Try
- slub_debug=,dentry_cache
+ slub_debug=,dentry
to only enable debugging on the dentry cache.
Red zoning and tracking may realign the slab. We can just apply sanity checks
to the dentry cache with
- slub_debug=F,dentry_cache
+ slub_debug=F,dentry
In case you forgot to enable debugging on the kernel command line: It is
possible to enable debugging manually when the kernel is up. Look at the