zsmalloc failure issue in low memory conditions

zsmalloc failure issue in low memory conditions

[Yonghai Huang]

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi, nugpta and all:
Sorry to distribute you, now I met zsmalloc failure issue in very low memory conditions, and i found someone already have met such issue, and have had discussions, but looks like no final patch for it, i don't know whether there are patches to fix it. could you give some advice on it?
Below is discussion link for it:
http://linux-kernel.2935.n7.nabble.com/zram-zsmalloc-issues-in-very-low-memory-conditions-td742009.html

With kind regards,
Yonghai

[-- Attachment #2: Type: text/html, Size: 4111 bytes --]

Re: zsmalloc failure issue in low memory conditions

[Nitin Gupta]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Hi Yonghai,

CC'ing the current maintainer, Minchan Kim.

Thanks,
Nitin

On 7/3/14, 5:03 PM, Yonghai Huang wrote:
>
> Hi, nugpta and all:
>
> Sorry to distribute you, now I met zsmalloc failure issue in very low 
> memory conditions, and i found someone already have met such issue, 
> and have had discussions, but looks like no final patch for it, i 
> don't know whether there are patches to fix it. could you give some 
> advice on it?
>
> Below is discussion link for it:
>
>
>   http://linux-kernel.2935.n7.nabble.com/zram-zsmalloc-issues-in-very-low-memory-conditions-td742009.html
>
> *//*
>
> */With kind regards,/*
>
> */Yonghai/*
>


[-- Attachment #2: Type: text/html, Size: 4717 bytes --]

Re: zsmalloc failure issue in low memory conditions

[Minchan Kim]

On Thu, Jul 03, 2014 at 08:24:27PM -0700, Nitin Gupta wrote:
> Hi Yonghai,
> 
> CC'ing the current maintainer, Minchan Kim.

Thanks for Ccing me, Nitin.

> 
> Thanks,
> Nitin
> 
> On 7/3/14, 5:03 PM, Yonghai Huang wrote:
> >
> >Hi, nugpta and all:
> >
> >Sorry to distribute you, now I met zsmalloc failure issue in very
> >low memory conditions, and i found someone already have met such
> >issue, and have had discussions, but looks like no final patch for
> >it, i don't know whether there are patches to fix it. could you
> >give some advice on it?
> >
> >Below is discussion link for it:
> >
> >
> >  http://linux-kernel.2935.n7.nabble.com/zram-zsmalloc-issues-in-very-low-memory-conditions-td742009.html
> >

At that time, I didn't have a time to look at it by biz trip but
reported twice until now so I'd like to bring up the issue.

zRAM works with reserved memory(ex, zone->low - zone->min) so
if you increased min_free_kbytes, maybe the problem would be gone
but it's not a proper fix, I think because if some of other(ex,
proprietary driver) deplete the reserved memory with __GFP_MEMALLOC
or PF_MEMALLOC, zsmalloc could be failed although it's rare
in current mainline but VM can reclaim file-backed pages still
so system can go without OOM kill while swap layer can emit lots
of warning message about failing write. :(

For me, ideal solution is to need to feedback loop from zram block
driver to VM via congestion control(Currently, reclaim of VM doesn't
consider swap backend's congestion state but not too hard to fix)
as Olav suggested but it has another issue to update uncongestion
state from zram side but finally we could find a solution, I believe. :)

But before diving into the implementation, I need to reproduce
the problem and maybe it would be helpful if you says your enviroment.

1. CPU
2. RAM size
3. zram disksize
4. /proc/sys/vm/page-cluster
5. /sys/block/zram0/max_comp_streams
6. what workload do you have?
7. /proc/zoneinfo
8. What kinds of file system do you use?
9. What kinds of workload do you have when the problem happens?
10. It would be really helpful if you can get /proc/vmstat when the problem happened.

Anyway, I will have a time to reproduce/investigate the problem next week
and get back to you.

Thanks for the report!

-- 
Kind regards,
Minchan Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>