On Tue 07-03-17 22:50:48, Tetsuo Handa wrote: > Michal Hocko wrote: > > From: Michal Hocko <mhocko@xxxxxxxx> > > > > We currently have 2 specific WQ_RECLAIM workqueues in the mm code. > > vmstat_wq for updating pcp stats and lru_add_drain_wq dedicated to drain > > per cpu lru caches. This seems more than necessary because both can run > > on a single WQ. Both do not block on locks requiring a memory allocation > > nor perform any allocations themselves. We will save one rescuer thread > > this way. > > > > On the other hand drain_all_pages() queues work on the system wq which > > doesn't have rescuer and so this depend on memory allocation (when all > > workers are stuck allocating and new ones cannot be created). This is > > not critical as there should be somebody invoking the OOM killer (e.g. > > the forking worker) and get the situation unstuck and eventually > > performs the draining. Quite annoying though. This worker should be > > using WQ_RECLAIM as well. We can reuse the same one as for lru draining > > and vmstat. > > Is "there should be somebody invoking the OOM killer" really true? in most cases there should be... I didn't say there will be... > According to http://lkml.kernel.org/r/201703031948.CHJ81278.VOHSFFFOOLJQMt@xxxxxxxxxxxxxxxxxxx > > kthreadd (PID = 2) is trying to allocate "struct task_struct" requested by > workqueue managers (PID = 19, 157, 10499) but is blocked on memory allocation. > > __GFP_FS allocations could get stuck waiting for drain_all_pages() ? > Also, order > 0 allocation request by the forking worker could get stuck > at too_many_isolated() in mm/compaction.c ? There might be some extreme cases which however do not change the justification of this patch. I didn't see such cases reported anywhere - other than in your stress testing where we do not really know what is going on yet - and so I didn't mention them and nor I have marked the patch for stable. I am wondering what is the point of this feedback actually? Do you see anything wrong in the patch or is this about the wording of the changelog? If it is the later is your concern serious enough to warrant the rewording/reposting? -- Michal Hocko SUSE Labs -- 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>
