aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/bcache.txt
diff options
context:
space:
mode:
authorAnatol Pomozov <anatol.pomozov@gmail.com>2013-05-08 19:56:16 -0400
committerJiri Kosina <jkosina@suse.cz>2013-05-28 06:02:12 -0400
commitf884ab15afdc5514e88105c92a4e2e1e6539869a (patch)
tree24d2bca7a44b4302ca30bdd460a222d677fe1e9b /Documentation/bcache.txt
parent7e21f14d179ee8973a9b18552854c9934fcbe370 (diff)
doc: fix misspellings with 'codespell' tool
Signed-off-by: Anatol Pomozov <anatol.pomozov@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/bcache.txt')
-rw-r--r--Documentation/bcache.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/bcache.txt b/Documentation/bcache.txt
index 77db8809bd96..2cdd4cfc6912 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
@@ -359,7 +359,7 @@ unregister
359SYSFS - CACHE SET INTERNAL: 359SYSFS - CACHE SET INTERNAL:
360 360
361This directory also exposes timings for a number of internal operations, with 361This directory also exposes timings for a number of internal operations, with
362separate files for average duration, average frequency, last occurence and max 362separate files for average duration, average frequency, last occurrence and max
363duration: garbage collection, btree read, btree node sorts and btree splits. 363duration: garbage collection, btree read, btree node sorts and btree splits.
364 364
365active_journal_entries 365active_journal_entries
@@ -414,7 +414,7 @@ freelist_percent
414 space. 414 space.
415 415
416io_errors 416io_errors
417 Number of errors that have occured, decayed by io_error_halflife. 417 Number of errors that have occurred, decayed by io_error_halflife.
418 418
419metadata_written 419metadata_written
420 Sum of all non data writes (btree writes and all other metadata). 420 Sum of all non data writes (btree writes and all other metadata).