Fix a typo max_cache_mb -> max_cached_mb, and update the documented
default value from 3/4 of client RAM to 1/2, which has been the
case since 2.6.
Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
Change-Id: Icfd269e18e52f6df27f681b4dc850d66023ebbe5
Reviewed-on: https://review.whamcloud.com/39825
Tested-by: jenkins <devops@whamcloud.com>
Reviewed-by: Vikentsi Lapa <vlapa@whamcloud.com>
</para>
</listitem>
<listitem>
- <para><literal>llite.<replaceable>fsname_instance</replaceable>.max_cache_mb</literal>
+ <para><literal>llite.<replaceable>fsname_instance</replaceable>.max_cached_mb</literal>
- Maximum amount of read+write data cached by the client. The
- default value is 3/4 of the client RAM.
+ default value is 1/2 of the client RAM.
</para>
</listitem>
</itemizedlist>