Clarify the fact that extent_cache and noextent_cache toggle
read extent cache on or off.
Cc: Bagas Sanjaya <bagasdo...@gmail.com>
Signed-off-by: Yangtao Li <frank...@vivo.com>
---
v3:
-update msg
Documentation/filesystems/f2fs.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/f2fs.rst
b/Documentation/filesystems/f2fs.rst
index c57745375edb..6db21ae0136a 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst
@@ -163,11 +163,11 @@ barrier If this option is set,
cache_flush commands are allowed to be
fastboot This option is used when a system wants to reduce mount
time as much as possible, even though normal
performance
can be sacrificed.
-extent_cache Enable an extent cache based on rb-tree, it can cache
- as many as extent which map between contiguous logical
+extent_cache Enable a read extent cache based on rb-tree. It can
cache
+ many extents which map between contiguous logical
address and physical address per inode, resulting in
increasing the cache hit ratio. Set by default.
-noextent_cache Disable an extent cache based on rb-tree explicitly,
see
+noextent_cache Disable a read extent cache based on rb-tree
explicitly, see
the above extent_cache mount option.
noinline_data Disable the inline data feature, inline data feature is
enabled by default.
--
2.39.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
