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, 7 Mar 2012 13:18:56 -0500
From:	Satoru Moriya <satoru.moriya@....com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	"jweiner@...hat.com" <jweiner@...hat.com>
CC:	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"riel@...hat.com" <riel@...hat.com>,
	"lwoodman@...hat.com" <lwoodman@...hat.com>,
	"shaohua.li@...el.com" <shaohua.li@...el.com>,
	"dle-develop@...ts.sourceforge.net" 
	<dle-develop@...ts.sourceforge.net>,
	Seiji Aguchi <seiji.aguchi@....com>
Subject: RE: [RFC][PATCH] avoid swapping out with swappiness==0

On 03/07/2012 12:19 PM, KOSAKI Motohiro wrote:
> On 3/5/2012 4:56 PM, Johannes Weiner wrote:
>> On Fri, Mar 02, 2012 at 12:36:40PM -0500, Satoru Moriya wrote:
>>>
>>> This patch changes the behavior with swappiness==0. If we set 
>>> swappiness==0, the kernel does not swap out completely (for global 
>>> reclaim until the amount of free pages and filebacked pages in a 
>>> zone has been reduced to something very very small (nr_free + 
>>> nr_filebacked < high watermark)).
>>>
>>> Any comments are welcome.
>>
>> Last time I tried that (getting rid of sc->may_swap, using 
>> !swappiness), it was rejected it as there were users who relied on 
>> swapping very slowly with this setting.
>>
>> KOSAKI-san, do I remember correctly?  Do you still think it's an 
>> issue?
>>
>> Personally, I still think it's illogical that !swappiness allows 
>> swapping and would love to see this patch go in.
> 
> Thank you. I brought back to memory it. Unfortunately DB folks are 
> still mainly using RHEL5 generation distros. At that time, swapiness=0 
> doesn't mean disabling swap.
> 
> They want, "don't swap as far as kernel has any file cache page". but 
> linux don't have such feature. then they used swappiness for emulate 
> it. So, I think this patch clearly make userland harm. Because of, we 
> don't have an alternative way.

If they expect the behavior that "don't swap as far as kernel
has any file cache page", this patch definitely helps them
because if we set swappiness==0, kernel does not swap out
*until* nr_free + nr_filebacked < high watermark in the zone.
It means kernel begins to swap out when nr_free + nr_filebacked
becomes less than high watermark.

But, yes, this patch actually changes the behavior with
swappiness==0 and so it may make userland harm. 

How about introducing new value e.g -1 to avoid swap and
maintain compatibility?

Regards,
Satoru
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ