linux-kernel - Re: [-mm PATCH 8/9] Memory controller add switch to control what type of pages to limit (v4)

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070813003348.91E3E1BF943@siro.lan>
Date:	Mon, 13 Aug 2007 09:33:48 +0900 (JST)
From:	yamamoto@...inux.co.jp (YAMAMOTO Takashi)
To:	balbir@...ux.vnet.ibm.com
Cc:	akpm@...ux-foundation.org, a.p.zijlstra@...llo.nl,
	dhaval@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, ebiederm@...ssion.com,
	containers@...ts.osdl.org, menage@...gle.com, xemul@...nvz.org
Subject: Re: [-mm PATCH 8/9] Memory controller add switch to control what type
	of pages to limit (v4)

> Choose if we want cached pages to be accounted or not. By default both
> are accounted for. A new set of tunables are added.
> 
> echo -n 1 > mem_control_type
> 
> switches the accounting to account for only mapped pages
> 
> echo -n 2 > mem_control_type
> 
> switches the behaviour back

MEM_CONTAINER_TYPE_ALL is 3, not 2.

YAMAMOTO Takashi

> +enum {
> +	MEM_CONTAINER_TYPE_UNSPEC = 0,
> +	MEM_CONTAINER_TYPE_MAPPED,
> +	MEM_CONTAINER_TYPE_CACHED,
> +	MEM_CONTAINER_TYPE_ALL,
> +	MEM_CONTAINER_TYPE_MAX,
> +} mem_control_type;
> +
> +static struct mem_container init_mem_container;

> +	mem = rcu_dereference(mm->mem_container);
> +	if (mem->control_type == MEM_CONTAINER_TYPE_ALL)
> +		return mem_container_charge(page, mm);
> +	else
> +		return 0;
-
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/