From: David Sterba Subject: Re: vmalloc with GFP_NOFS Date: Wed, 9 May 2018 16:13:34 +0200 Message-ID: <20180509141333.onn7rbaitzspjmsa@twin.jikos.cz> References: <20180424162712.GL17484@dhcp22.suse.cz> <20180424183536.GF30619@thunk.org> <20180424192542.GS17484@dhcp22.suse.cz> <20180509134222.GU32366@dhcp22.suse.cz> Reply-To: dsterba@suse.cz Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Theodore Y. Ts'o" , LKML , Artem Bityutskiy , Richard Weinberger , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Cyrille Pitchen , Andreas Dilger , Steven Whitehouse , Bob Peterson , Trond Myklebust , Anna Schumaker , Adrian Hunter , Philippe Ombredanne , Kate Stewart , Mikulas Patocka , To: Michal Hocko Return-path: Content-Disposition: inline In-Reply-To: <20180509134222.GU32366@dhcp22.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Wed, May 09, 2018 at 03:42:22PM +0200, Michal Hocko wrote: > On Tue 24-04-18 13:25:42, Michal Hocko wrote: > [...] > > > As a suggestion, could you take > > > documentation about how to convert to the memalloc_nofs_{save,restore} > > > scope api (which I think you've written about e-mails at length > > > before), and put that into a file in Documentation/core-api? > > > > I can. > > Does something like the below sound reasonable/helpful? Sounds good to me and matches how we've been using the vmalloc/nofs so far.