On (22/08/09 17:43), Sergey Senozhatsky wrote: > On (22/08/09 10:12), Jiri Slaby wrote: > > > So currently, I blame: > > > commit e7be8d1dd983156bbdd22c0319b71119a8fbb697 > > > Author: Alexey Romanov <avromanov@xxxxxxxxxxxxxx> > > > Date: Thu May 12 20:23:07 2022 -0700 > > > > > > zram: remove double compression logic > > > > > > > > > /me needs to confirm. > > > > With that commit reverted, I see no more I/O errors, only oom-killer > > messages (which is OK IMO, provided I write 1G of urandom on a machine w/ > > 800M of RAM): > > Hmm... So handle allocation always succeeds in the slow path? (when we > try to allocate it second time) Yeah I can see how handle re-allocation with direct reclaim can make it more successful, but in exchange it oom-kills some user-space process, I suppose. Is oom-kill really a good alternative though?
