Hi, On 4/16/23 21:03, Yangtao Li wrote: > Let's descrbie it's read extent cache. > > Signed-off-by: Yangtao Li <frank.li@xxxxxxxx> > --- > Documentation/filesystems/f2fs.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst > index c57745375edb..f68337086dec 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 > +extent_cache Enable an read extent cache based on rb-tree, it can cache Enable a read extent cache based on rb-tree. It can cache > as many as extent which map between contiguous logical I don't know that that is trying to say. Maybe this? many extents which map between contiguous logical Does it cache many extents or all of them? If all of them, then maybe this? the 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 an read extent cache based on rb-tree explicitly, see 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. -- ~Randy
