diff options
author | Masanari Iida <standby24x7@gmail.com> | 2013-05-20 00:04:35 +0900 |
---|---|---|
committer | Kent Overstreet <koverstreet@google.com> | 2013-06-26 21:58:04 -0700 |
commit | bd206b51bca1e0a1c5f4b00218d56213a1f6d3bd (patch) | |
tree | 28627279d71c74c0dab8ebca3f44f702bf99a546 | |
parent | 72c270612bd33192fa836ad0f2939af1ca218292 (diff) | |
download | linux-bd206b51bca1e0a1c5f4b00218d56213a1f6d3bd.tar.bz2 |
doc: Fix typo in documentation/bcache.txt
Correct spelling typo in documentation/bcache.txt
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
-rw-r--r-- | Documentation/bcache.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/bcache.txt b/Documentation/bcache.txt index b3a7e7d384f6..c3365f26b2d9 100644 --- a/Documentation/bcache.txt +++ b/Documentation/bcache.txt @@ -181,7 +181,7 @@ want for getting the best possible numbers when benchmarking. In practice this isn't an issue because as soon as a write comes along it'll cause the btree node to be split, and you need almost no write traffic for - this to not show up enough to be noticable (especially since bcache's btree + this to not show up enough to be noticeable (especially since bcache's btree nodes are huge and index large regions of the device). But when you're benchmarking, if you're trying to warm the cache by reading a bunch of data and there's no other traffic - that can be a problem. @@ -222,7 +222,7 @@ running it's in passthrough mode or caching). sequential_cutoff - A sequential IO will bypass the cache once it passes this threshhold; the + A sequential IO will bypass the cache once it passes this threshold; the most recent 128 IOs are tracked so sequential IO can be detected even when it isn't all done at once. @@ -296,7 +296,7 @@ cache_miss_collisions since the synchronization for cache misses was rewritten) cache_readaheads - Count of times readahead occured. + Count of times readahead occurred. SYSFS - CACHE SET: @@ -362,7 +362,7 @@ unregister SYSFS - CACHE SET INTERNAL: This directory also exposes timings for a number of internal operations, with -separate files for average duration, average frequency, last occurence and max +separate files for average duration, average frequency, last occurrence and max duration: garbage collection, btree read, btree node sorts and btree splits. active_journal_entries @@ -417,7 +417,7 @@ freelist_percent space. io_errors - Number of errors that have occured, decayed by io_error_halflife. + Number of errors that have occurred, decayed by io_error_halflife. metadata_written Sum of all non data writes (btree writes and all other metadata). |