On Tue, Aug 27, 2024 at 08:01:32AM GMT, Michal Hocko wrote: > You are not really answering the main concern I have brought up though. > I.e. GFP_NOFAIL being fundamentally incompatible with NORECLAIM semantic > because the page allocator doesn't and will not support this allocation > mode. Scoped noreclaim semantic makes such a use much less visible > because it can be deep in the scoped context there more error prone to > introduce thus making the code harder to maintain. You're too attached to GFP_NOFAIL. GFP_NOFAIL is something we very rarely use, and it's not something we want to use. Furthermore, GFP_NOFAIL allocations can fail regardless of this patch - e.g. if it's more than 2 pages, it's not going to be GFP_NOFAIL. In general you can't avoid having error paths for memory allocations, and GFP_NOFAIL can't fundamentally change that. Stop trying to design things around GFP_NOFAIL. > I do see why you would like to have NOWAIT kvmalloc support available > and I also do see challenges in achieving that. But I completely fail to > see why you are bring that up _here_ as that is not really relevant to > PF_MEMALLOC_NORECLAIM use by bcachefs because it demonstrably doesn't > need that. There is no other user of the flag at the moment so dropping > the flag before there is more misuse is a reasonable goal. If you want > to bring up vmalloc NOWAIT support then feel free to do that in another > context and we can explore potential ways to achieve that. The inconsistencies between what PF_MEMALLOC supports and what gfp flags support are quite relevant. If gfp flags aren't plumbed everywhere, and aren't going to be plumbed everywhere (and that is the current decision), then we must have PF_MEMALLOC support.
