linux-kernel - RE: [RFC v3 0/3] vmpressure_fd: Linux VM pressure notifications

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]

Date:	Wed, 21 Nov 2012 13:48:14 +0000
From:	<leonid.moiseichuk@...ia.com>
To:	<glommer@...allels.com>
CC:	<kirill@...temov.name>, <rientjes@...gle.com>,
	<anton.vorontsov@...aro.org>, <penberg@...nel.org>,
	<mgorman@...e.de>, <kosaki.motohiro@...il.com>,
	<minchan@...nel.org>, <b.zolnierkie@...sung.com>,
	<john.stultz@...aro.org>, <linux-mm@...ck.org>,
	<linux-kernel@...r.kernel.org>, <linaro-kernel@...ts.linaro.org>,
	<patches@...aro.org>, <kernel-team@...roid.com>,
	<linux-man@...r.kernel.org>, <kamezawa.hiroyu@...fujitsu.com>,
	<mhocko@...e.cz>, <hannes@...xchg.org>, <tj@...nel.org>
Subject: RE: [RFC v3 0/3] vmpressure_fd: Linux VM pressure notifications


-----Original Message-----
From: ext Glauber Costa [mailto:glommer@...allels.com] 
Sent: 21 November, 2012 13:55
....
So I'll say it again: if this is always global, there is no reason any
cgroup needs to be involved. If this turns out to be per-process, as
Anton suggested in a recent e-mail, I don't see any reason to have
cgroups involved as well.
-----

Per-process memory tracking has no much sense: process should consume all available memory but work fast. Also this approach required knowledge about process deps to take into account dependencies e.g. in dbus or Xorg. If you need to know how much memory process consumed in particular moment you can use /proc/self/smaps, that is easier.

Best Wishes,
Leonid
--
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/