Re: [PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Damien Wyart
* Sonny Rao [2012-11-19 10:44]: > Damien, thanks for testing and finding that bug. If you could, please > give this version a try, thanks. Tried it for a few hours (as soon as the min/max problem was suggested on the list) and the previous problems disappeared. -- Damien -- To unsubscribe

Re: [PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Sonny Rao
On Mon, Nov 19, 2012 at 10:41 AM, Sonny Rao wrote: > The system uses global_dirtyable_memory() to calculate > number of dirtyable pages/pages that can be allocated > to the page cache. A bug causes an underflow thus making > the page count look like a big unsigned number. This in turn >

[PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Sonny Rao
The system uses global_dirtyable_memory() to calculate number of dirtyable pages/pages that can be allocated to the page cache. A bug causes an underflow thus making the page count look like a big unsigned number. This in turn confuses the dirty writeback throttling to aggressively write back

[PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Sonny Rao
The system uses global_dirtyable_memory() to calculate number of dirtyable pages/pages that can be allocated to the page cache. A bug causes an underflow thus making the page count look like a big unsigned number. This in turn confuses the dirty writeback throttling to aggressively write back

Re: [PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Sonny Rao
On Mon, Nov 19, 2012 at 10:41 AM, Sonny Rao sonny...@chromium.org wrote: The system uses global_dirtyable_memory() to calculate number of dirtyable pages/pages that can be allocated to the page cache. A bug causes an underflow thus making the page count look like a big unsigned number. This

Re: [PATCHv5] mm: Fix calculation of dirtyable memory

2012-11-19 Thread Damien Wyart
* Sonny Rao sonny...@chromium.org [2012-11-19 10:44]: Damien, thanks for testing and finding that bug. If you could, please give this version a try, thanks. Tried it for a few hours (as soon as the min/max problem was suggested on the list) and the previous problems disappeared. -- Damien --