Messages in this thread | | | Date | Wed, 18 Nov 2015 10:22:20 +0100 | From | Michal Hocko <> | Subject | Re: [PATCH 2/2] mm: do not loop over ALLOC_NO_WATERMARKS without triggering reclaim |
| |
On Wed 18-11-15 10:11:01, Michal Hocko wrote: > Besides that I fail to see why a work item would ever > want to set PF_MEMALLOC for legitimate reasons. I have done a quick git > grep over the tree and there doesn't seem to be any user.
OK, I have missed one case. xfs_btree_split_worker is really setting PF_MEMALLOC from the worker context basically to inherit the flag from kswapd. This is a legitimate use but it doesn't affect the allocation path so it is not related to this discussion. -- Michal Hocko SUSE Labs
| |