aboutsummaryrefslogtreecommitdiff
path: root/system/bcache-tools
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 11:59:12 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:03 -0400
commit629dabb17c5b74c8ce751ebfacecc042926af973 (patch)
tree92b6c016b7a4ac293a84964e46cb30abe9ffea57 /system/bcache-tools
parent894c1fc4c5c874111eaade4a556ef6a4113d0b33 (diff)
system/bcache-tools: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/bcache-tools')
-rw-r--r--system/bcache-tools/README27
1 files changed, 14 insertions, 13 deletions
diff --git a/system/bcache-tools/README b/system/bcache-tools/README
index 7db39a5263ae1..251f258a39348 100644
--- a/system/bcache-tools/README
+++ b/system/bcache-tools/README
@@ -1,20 +1,21 @@
These are the userspace tools required for bcache.
-Bcache is a patch for the Linux kernel to use SSDs to cache other block
-devices. For more information, see http://bcache.evilpiepirate.org.
-Documentation for the run time interface is included in the kernel tree, in
-Documentation/bcache.txt.
+Bcache is a patch for the Linux kernel to use SSDs
+to cache other block devices. For more information, see
+http://bcache.evilpiepirate.org. Documentation for the run time
+interface is included in the kernel tree, in Documentation/bcache.txt.
Included:
make-bcache
-Formats a block device for use with bcache. A device can be formatted for use
-as a cache or as a backing device (requires yet to be implemented kernel
-support). The most important option is for specifying the bucket size.
-Allocation is done in terms of buckets, and cache hits are counted per bucket;
-thus a smaller bucket size will give better cache utilization, but poorer write
-performance. The bucket size is intended to be equal to the size of your SSD's
-erase blocks, which seems to be 128k-512k for most SSDs; feel free to
+Formats a block device for use with bcache. A device can be
+formatted for use as a cache or as a backing device (requires yet
+to be implemented kernel support). The most important option is for
+specifying the bucket size. Allocation is done in terms of buckets,
+and cache hits are counted per bucket; thus a smaller bucket size
+will give better cache utilization, but poorer write performance. The
+bucket size is intended to be equal to the size of your SSD's erase
+blocks, which seems to be 128k-512k for most SSDs; feel free to
experiment.
bcache-super-show
@@ -22,9 +23,9 @@ Prints the bcache superblock of a cache device or a backing device.
Udev rules
The first half of the rules do auto-assembly and add uuid symlinks
-to cache and backing devices. If util-linux's libblkid is
+to cache and backing devices. If util-linux's libblkid is
sufficiently recent (2.24) the rules will take advantage of
-the fact that bcache has already been detected. Otherwise
+the fact that bcache has already been detected. Otherwise
they call a small probe-bcache program that imitates blkid.
The second half of the rules add symlinks to cached devices,