Re: [to-be-updated] zram_drv-add-__gfp_nomemalloc-not-to-use-alloc_no_watermarks.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jaewon,

On Fri, Jun 17, 2022 at 10:04:32AM +0900, Jaewon Kim wrote:
> 
> 
> Dear Minchan Kim
> 
> I'm sorry but I got reported this atomic alloation failure again recently.
> I asked network develeper to implement a work around though.
> I just hope to get your signed-off if you don't mind.
> 
> Thank you
> Jaewon Kim

As I mentioned, GFP_ATOMIC allocation could be easily failed due to
reclaim constraint, the user should carry on the fallback plan.

The atomic allocation could also fail not only zram but also other
sources if they try to allocate GFP_ATOMIC.

The suggested patch could affect other existing zram workloads a lot
(which would be common than rare atomic allocation failure) so 
I don't want to accept the patch.

Thank you.



[Index of Archives]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux