| 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
| ||
|
Date: Wed, 24 Sep 2014 19:14:21 +0400 From: Vladimir Davydov <vdavydov@...allels.com> To: Johannes Weiner <hannes@...xchg.org> CC: Andrew Morton <akpm@...ux-foundation.org>, Greg Thelen <gthelen@...gle.com>, Dave Hansen <dave@...1.net>, Michal Hocko <mhocko@...e.cz>, <linux-mm@...ck.org>, <cgroups@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [patch 2/3] mm: memcontrol: simplify detecting when the memory+swap limit is hit On Wed, Sep 24, 2014 at 11:08:57AM -0400, Johannes Weiner wrote: > When attempting to charge pages, we first charge the memory counter > and then the memory+swap counter. If one of the counters is at its > limit, we enter reclaim, but if it's the memory+swap counter, reclaim > shouldn't swap because that wouldn't change the situation. However, > if the counters have the same limits, we never get to the memory+swap > limit. To know whether reclaim should swap or not, there is a state > flag that indicates whether the limits are equal and whether hitting > the memory limit implies hitting the memory+swap limit. > > Just try the memory+swap counter first. > > Signed-off-by: Johannes Weiner <hannes@...xchg.org> Reviewed-by: Vladimir Davydov <vdavydov@...allels.com> -- 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/
Powered by blists - more mailing lists