aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2013-05-19 11:04:35 -0400
committerKent Overstreet <koverstreet@google.com>2013-06-27 00:58:04 -0400
commitbd206b51bca1e0a1c5f4b00218d56213a1f6d3bd (patch)
tree28627279d71c74c0dab8ebca3f44f702bf99a546 /Documentation
parent72c270612bd33192fa836ad0f2939af1ca218292 (diff)
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>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/bcache.txt10
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.
181 181
182 In practice this isn't an issue because as soon as a write comes along it'll 182 In practice this isn't an issue because as soon as a write comes along it'll
183 cause the btree node to be split, and you need almost no write traffic for 183 cause the btree node to be split, and you need almost no write traffic for
184 this to not show up enough to be noticable (especially since bcache's btree 184 this to not show up enough to be noticeable (especially since bcache's btree
185 nodes are huge and index large regions of the device). But when you're 185 nodes are huge and index large regions of the device). But when you're
186 benchmarking, if you're trying to warm the cache by reading a bunch of data 186 benchmarking, if you're trying to warm the cache by reading a bunch of data
187 and there's no other traffic - that can be a problem. 187 and there's no other traffic - that can be a problem.
@@ -222,7 +222,7 @@ running
222 it's in passthrough mode or caching). 222 it's in passthrough mode or caching).
223 223
224sequential_cutoff 224sequential_cutoff
225 A sequential IO will bypass the cache once it passes this threshhold; the 225 A sequential IO will bypass the cache once it passes this threshold; the
226 most recent 128 IOs are tracked so sequential IO can be detected even when 226 most recent 128 IOs are tracked so sequential IO can be detected even when
227 it isn't all done at once. 227 it isn't all done at once.
228 228
@@ -296,7 +296,7 @@ cache_miss_collisions
296 since the synchronization for cache misses was rewritten) 296 since the synchronization for cache misses was rewritten)
297 297
298cache_readaheads 298cache_readaheads
299 Count of times readahead occured. 299 Count of times readahead occurred.
300 300
301SYSFS - CACHE SET: 301SYSFS - CACHE SET:
302 302
@@ -362,7 +362,7 @@ unregister
362SYSFS - CACHE SET INTERNAL: 362SYSFS - CACHE SET INTERNAL:
363 363
364This directory also exposes timings for a number of internal operations, with 364This directory also exposes timings for a number of internal operations, with
365separate files for average duration, average frequency, last occurence and max 365separate files for average duration, average frequency, last occurrence and max
366duration: garbage collection, btree read, btree node sorts and btree splits. 366duration: garbage collection, btree read, btree node sorts and btree splits.
367 367
368active_journal_entries 368active_journal_entries
@@ -417,7 +417,7 @@ freelist_percent
417 space. 417 space.
418 418
419io_errors 419io_errors
420 Number of errors that have occured, decayed by io_error_halflife. 420 Number of errors that have occurred, decayed by io_error_halflife.
421 421
422metadata_written 422metadata_written
423 Sum of all non data writes (btree writes and all other metadata). 423 Sum of all non data writes (btree writes and all other metadata).