On Fri 12-01-18 13:41:33, Sergey Senozhatsky wrote:
> On (01/08/18 19:22), Sergey Senozhatsky wrote:
> [..]
> > > Your changelog is rather modest on the information.
> >
> > fair point!
> >
> > > Could you be more specific on how the problem actually happens how
> > > likely it is?
> >
> > ok.
On Fri 12-01-18 13:41:33, Sergey Senozhatsky wrote:
> On (01/08/18 19:22), Sergey Senozhatsky wrote:
> [..]
> > > Your changelog is rather modest on the information.
> >
> > fair point!
> >
> > > Could you be more specific on how the problem actually happens how
> > > likely it is?
> >
> > ok.
On (01/08/18 19:22), Sergey Senozhatsky wrote:
[..]
> > Your changelog is rather modest on the information.
>
> fair point!
>
> > Could you be more specific on how the problem actually happens how
> > likely it is?
>
> ok. so what we have is
>
> slow_path / swap-out page
>
On (01/08/18 19:22), Sergey Senozhatsky wrote:
[..]
> > Your changelog is rather modest on the information.
>
> fair point!
>
> > Could you be more specific on how the problem actually happens how
> > likely it is?
>
> ok. so what we have is
>
> slow_path / swap-out page
>
On (01/08/18 09:37), Michal Hocko wrote:
[..]
> > the lockup is not the main problem and I'm not really trying to
> > address it here. we simply can fill up the entire kernel logbuf
> > with the same "Write-error on swap-device" errors.
>
> Your changelog is rather modest on the information.
On (01/08/18 09:37), Michal Hocko wrote:
[..]
> > the lockup is not the main problem and I'm not really trying to
> > address it here. we simply can fill up the entire kernel logbuf
> > with the same "Write-error on swap-device" errors.
>
> Your changelog is rather modest on the information.
On Mon 08-01-18 10:58:18, Sergey Senozhatsky wrote:
> On (01/06/18 14:34), Michal Hocko wrote:
> > > zsmalloc allocation is just one possibility; an error in
> > > compressing algorithm is another one, yet is rather unlikely.
> > > most likely it's OOM which can cause problems. but in any case
> >
On Mon 08-01-18 10:58:18, Sergey Senozhatsky wrote:
> On (01/06/18 14:34), Michal Hocko wrote:
> > > zsmalloc allocation is just one possibility; an error in
> > > compressing algorithm is another one, yet is rather unlikely.
> > > most likely it's OOM which can cause problems. but in any case
> >
On (01/06/18 14:34), Michal Hocko wrote:
> > zsmalloc allocation is just one possibility; an error in
> > compressing algorithm is another one, yet is rather unlikely.
> > most likely it's OOM which can cause problems. but in any case
> > it's sort of unclear what should be done. an error can be a
On (01/06/18 14:34), Michal Hocko wrote:
> > zsmalloc allocation is just one possibility; an error in
> > compressing algorithm is another one, yet is rather unlikely.
> > most likely it's OOM which can cause problems. but in any case
> > it's sort of unclear what should be done. an error can be a
On Sat 06-01-18 19:03:13, Sergey Senozhatsky wrote:
> Hello,
>
> On (01/06/18 10:41), Michal Hocko wrote:
> > On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> > > Use the ratelimited printk() version for swap-device write error
> > > reporting. We can use ZRAM as a swap-device, and the
On Sat 06-01-18 19:03:13, Sergey Senozhatsky wrote:
> Hello,
>
> On (01/06/18 10:41), Michal Hocko wrote:
> > On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> > > Use the ratelimited printk() version for swap-device write error
> > > reporting. We can use ZRAM as a swap-device, and the
Hello,
On (01/06/18 10:41), Michal Hocko wrote:
> On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> > Use the ratelimited printk() version for swap-device write error
> > reporting. We can use ZRAM as a swap-device, and the tricky part
> > here is that zsmalloc() stores compressed objects in
Hello,
On (01/06/18 10:41), Michal Hocko wrote:
> On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> > Use the ratelimited printk() version for swap-device write error
> > reporting. We can use ZRAM as a swap-device, and the tricky part
> > here is that zsmalloc() stores compressed objects in
On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> Use the ratelimited printk() version for swap-device write error
> reporting. We can use ZRAM as a swap-device, and the tricky part
> here is that zsmalloc() stores compressed objects in memory, thus
> it has to allocates pages during swap-out.
On Sat 06-01-18 13:34:07, Sergey Senozhatsky wrote:
> Use the ratelimited printk() version for swap-device write error
> reporting. We can use ZRAM as a swap-device, and the tricky part
> here is that zsmalloc() stores compressed objects in memory, thus
> it has to allocates pages during swap-out.
Use the ratelimited printk() version for swap-device write error
reporting. We can use ZRAM as a swap-device, and the tricky part
here is that zsmalloc() stores compressed objects in memory, thus
it has to allocates pages during swap-out. If the system is short
on memory, then we begin to flood
Use the ratelimited printk() version for swap-device write error
reporting. We can use ZRAM as a swap-device, and the tricky part
here is that zsmalloc() stores compressed objects in memory, thus
it has to allocates pages during swap-out. If the system is short
on memory, then we begin to flood
18 matches
Mail list logo
