Lines Matching +full:blocking +full:- +full:io

4 GFP masks used from FS/IO context
13 Code paths in the filesystem and IO stacks must be careful when
15 memory reclaim calling back into the FS or IO paths and blocking on
16 already held resources (e.g. locks - most commonly those used for the
25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
36 mask so no memory allocation can recurse back in the FS/IO.
38 .. kernel-doc:: include/linux/sched/mm.h
40 .. kernel-doc:: include/linux/sched/mm.h
43 FS/IO code then simply calls the appropriate save function before
44 any critical section with respect to the reclaim is started - e.g.
59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial