| 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
| ||
|
Message-ID: <4DD054EF.4020300@redhat.com> Date: Sun, 15 May 2011 18:34:23 -0400 From: Rik van Riel <riel@...hat.com> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> CC: linux-mm@...ck.org, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, kamezawa.hiroyu@...fujitsu.com, minchan.kim@...il.com Subject: Re: [PATCH 3/3] vmscan: implement swap token priority decay On 05/13/2011 07:42 AM, KOSAKI Motohiro wrote: > While testing for memcg aware swap token, I observed a swap token > was often grabbed an intermittent running process (eg init, auditd) > and they never release a token. > > Why? Currently, swap toke priority is only decreased at page fault > path. Then, if the process sleep immediately after to grab swap > token, their swap token priority never be decreased. That makes > obviously undesired result. > > This patch implement very poor (and lightweight) priority decay > mechanism. It only be affect to the above corner case and doesn't > change swap tendency workload performance (eg multi process qsbench > load) Ohhh, good catch. The original swap token algorithm did not have this problem, and I never caught the fact that the replacement (which is better in many ways) does... > Signed-off-by: KOSAKI Motohiro<kosaki.motohiro@...fujitsu.com> Reviewed-by: Rik van Riel<riel@...hat.com> -- All rights reversed -- 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