summaryrefslogtreecommitdiff
path: root/Documentation/filesystems/logfs.txt
diff options
context:
space:
mode:
authorAnand Gadiyar <gadiyar@ti.com>2010-05-10 14:51:19 +0530
committerJiri Kosina <jkosina@suse.cz>2010-05-10 11:56:30 +0200
commita8cd4561ea176f51e9f4707873ca4eff8fd5ee70 (patch)
tree82f4f90f732fcc06480073bf494bab503fc24d62 /Documentation/filesystems/logfs.txt
parent7d7fb0e6eb78600e5d4fb0f28858e97d38ef6bbf (diff)
fix "seperate" typos in comments
s/seperate/separate Signed-off-by: Anand Gadiyar <gadiyar@ti.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/filesystems/logfs.txt')
-rw-r--r--Documentation/filesystems/logfs.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/filesystems/logfs.txt b/Documentation/filesystems/logfs.txt
index e64c94ba401a..bca42c22a143 100644
--- a/Documentation/filesystems/logfs.txt
+++ b/Documentation/filesystems/logfs.txt
@@ -59,7 +59,7 @@ Levels
------
Garbage collection (GC) may fail if all data is written
-indiscriminately. One requirement of GC is that data is seperated
+indiscriminately. One requirement of GC is that data is separated
roughly according to the distance between the tree root and the data.
Effectively that means all file data is on level 0, indirect blocks
are on levels 1, 2, 3 4 or 5 for 1x, 2x, 3x, 4x or 5x indirect blocks,
@@ -67,7 +67,7 @@ respectively. Inode file data is on level 6 for the inodes and 7-11
for indirect blocks.
Each segment contains objects of a single level only. As a result,
-each level requires its own seperate segment to be open for writing.
+each level requires its own separate segment to be open for writing.
Inode File
----------
@@ -106,9 +106,9 @@ Vim
---
By cleverly predicting the life time of data, it is possible to
-seperate long-living data from short-living data and thereby reduce
+separate long-living data from short-living data and thereby reduce
the GC overhead later. Each type of distinc life expectency (vim) can
-have a seperate segment open for writing. Each (level, vim) tupel can
+have a separate segment open for writing. Each (level, vim) tupel can
be open just once. If an open segment with unknown vim is encountered
at mount time, it is closed and ignored henceforth.