Messages in this thread | | | Date | Mon, 23 Nov 2015 15:40:29 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH v3] zram: try vmalloc() after kmalloc() |
| |
On Tue, 24 Nov 2015 08:28:57 +0900 Minchan Kim <minchan@kernel.org> wrote:
> > What's the reasoning behind the modification to the gfp flags? > > > > It clears __GFP_FS, __GFP_IO and even __GFP_WAIT. I suspect the latter > > two (at least) can be retained. And given that vmalloc() uses > > This function is used in swapout and fs write path so we couldn't use > those flags.
We can use __GFP_RECLAIM (used to be __GFP_WAIT). That permits the allocation to wait for in-flight IO to complete and to reclaim clean pagecache.
| |