On Mon, Apr 12, 2021 at 02:23:30PM +0200, Daniel Wagner wrote: > Drop the WQ_MEM_RECLAIM flag as it is not needed and introduces > warnings. > > The documentation says "all wq which might be used in the memory > reclaim paths MUST have this flag set. The wq is guaranteed to have at > least one execution context regardless of memory pressure." > > By setting WQ_MEM_RECLAIM the threads are ready be running during > early init. The claim it guarantees at least one execution context > regardless of memory pressure is not supported by the implementation. > > As the nvme core does not depend on early init we can remove the > WQ_MEM_RECLAIM flag. This resolves a warning in the rdma path:
What does early init have to do with WQ_MEM_RECLAIM? WQ_MEM_RECLIAM is required when any thread in a reclaim context goes to sleep waiting for a WQ to complete. For instance by calling flush_workqueue() or many other things. The sleeping reclaim context must be guarenteed that the work can be completed without the work, work queue machinery, or anything the work has become interconnected with, recursing back into a reclaim. IIRC the issue here was some destroy or flush work in some error condition that happened to be under a reclaim context? I don't see the kind of analysis I'd expect in this commit message to justify this change. Jason
