Re: Re: why use alloc_workqueue instead of create_singlethread_workqueue to create nvme_workq

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

 



On Wed, Jun 01, 2016 at 10:54:27AM +0800, shhuiw@xxxxxxxxxxx wrote:
> Thanks, Keith!
> 
> Any idea on how to fix the warning? Just drop the WQ_MEM_RECLAIM for nvme_workq, or
> lru drain work schedule should be changed?

I sent request to lkml and linux-mm list, trying to resurrect this older
proposal from Tejun Heo:

  https://patchwork.ozlabs.org/patch/574623/

Not much interest yet, though.

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



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]