Bug#695182: [PATCH] Negative (setpoint-dirty) in bdi_position_ratio()

2013-01-24 Thread Fengguang Wu
On Fri, Jan 25, 2013 at 10:43:45AM +1100, paul.sz...@sydney.edu.au wrote: > Dear Fengguang, > > > Or more simple, you may show us the OOM dmesg which will contain the > > number of dirty pages. ... > > Do you mean kern.log lines like: Yes. > [ 744.754199] bash invoked oom-killer: gfp_mask=0xd0

Bug#695182: [PATCH] Negative (setpoint-dirty) in bdi_position_ratio()

2013-01-24 Thread Fengguang Wu
Hi Paul, > (This patch does not solve the PAE OOM issue.) You may try the below debug patch. The only way the writeback patches should trigger OOM, I think, is for the number of dirty/writeback pages going out of control. Or more simple, you may show us the OOM dmesg which will contain the numbe

Bug#695182: [PATCH] Negative (setpoint-dirty) in bdi_position_ratio()

2013-01-24 Thread Fengguang Wu
On Wed, Jan 23, 2013 at 12:54:38AM +0100, Jan Kara wrote: > On Sun 20-01-13 11:02:10, paul.sz...@sydney.edu.au wrote: > > In bdi_position_ratio(), get difference (setpoint-dirty) right even when > > negative. Both setpoint and dirty are unsigned long, the difference was > > zero-padded thus wrongly