Re: [PATCH v3] zram: try vmalloc() after kmalloc()

From: Andrew Morton
Date: Mon Nov 23 2015 - 18:40:35 EST

On Tue, 24 Nov 2015 08:28:57 +0900 Minchan Kim <minchan@xxxxxxxxxx> 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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at