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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20151123154029.ec1cb910a827ddf51aa986c4@linux-foundation.org>
Date:	Mon, 23 Nov 2015 15:40:29 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Kyeongdon Kim <kyeongdon.kim@....com>, ngupta@...are.org,
	sergey.senozhatsky.work@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] zram: try vmalloc() after kmalloc()

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/