linux-kernel - Re: [PATCH 8/8] doc: update Documentation/sysctl/vm.txt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 17 Jun 2014 09:20:40 +0800
From:	Xishi Qiu <qiuxishi@...wei.com>
To:	Randy Dunlap <rdunlap@...radead.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Wanpeng Li <liwanp@...ux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	<aquini@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
	Rik van Riel <riel@...hat.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Michal Hocko <mhocko@...e.cz>, Linux MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Li Zefan <lizefan@...wei.com>
Subject: Re: [PATCH 8/8] doc: update Documentation/sysctl/vm.txt

On 2014/6/17 0:57, Randy Dunlap wrote:

> On 06/16/14 02:25, Xishi Qiu wrote:
>> Update the doc.
>>
>> Signed-off-by: Xishi Qiu <qiuxishi@...wei.com>
>> ---
>>  Documentation/sysctl/vm.txt |   43 +++++++++++++++++++++++++++++++++++++++++++
>>  1 files changed, 43 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
>> index dd9d0e3..8008e53 100644
>> --- a/Documentation/sysctl/vm.txt
>> +++ b/Documentation/sysctl/vm.txt
>> @@ -20,6 +20,10 @@ Currently, these files are in /proc/sys/vm:
>>  
>>  - admin_reserve_kbytes
>>  - block_dump
>> +- cache_limit_mbytes
>> +- cache_limit_ratio
>> +- cache_reclaim_s
>> +- cache_reclaim_weight
>>  - compact_memory
>>  - dirty_background_bytes
>>  - dirty_background_ratio
>> @@ -97,6 +101,45 @@ information on block I/O debugging is in Documentation/laptops/laptop-mode.txt.
>>  
>>  ==============================================================
>>  
>> +cache_limit_mbytes
>> +
>> +This is used to limit page cache amount. The input unit is MB, value range
>> +is from 0 to totalram_pages. If this is set to 0, it will not limit page cache.
> 
> Where does one find the value of totalram_pages?
> 

"cat /proc/meminfo | grep MemTotal" or "free -m"

> Is totalram_pages in MB or does totalram_pages need to be divided by some value
> to convert it to MB?
> 

Yes, should convert it to MB.

Thanks,
Xishi Qiu

>> +When written to the file, cache_limit_ratio will be updated too.
>> +
>> +The default value is 0.
>> +
>> +==============================================================
>> +
>> +cache_limit_ratio
>> +
>> +This is used to limit page cache amount. The input unit is percent, value
>> +range is from 0 to 100. If this is set to 0, it will not limit page cache.
>> +When written to the file, cache_limit_mbytes will be updated too.
>> +
>> +The default value is 0.
>> +
>> +==============================================================
>> +
>> +cache_reclaim_s
>> +
>> +This is used to reclaim page cache in circles. The input unit is second,
>> +the minimum value is 0. If this is set to 0, it will disable the feature.
>> +
>> +The default value is 0.
>> +
>> +==============================================================
>> +
>> +cache_reclaim_weight
>> +
>> +This is used to speed up page cache reclaim. It depend on enabling
> 
>                                                    depends on
> 
>> +cache_limit_mbytes/cache_limit_ratio or cache_reclaim_s. Value range is
>> +from 1(slow) to 100(fast).
>> +
>> +The default value is 1.
>> +
>> +==============================================================
>> +
>>  compact_memory
>>  
>>  Available only when CONFIG_COMPACTION is set. When 1 is written to the file,
>>
> 
> 



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/