Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3132056imm; Tue, 29 May 2018 01:23:29 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoF1zqNIgDtJDIsq97ngFwRXaykV3bYVS8Ky7SEenT3RJJWQtIjMK8krxbVPYbT5SMx1dk9 X-Received: by 2002:a17:902:2805:: with SMTP id e5-v6mr16901243plb.55.1527582209475; Tue, 29 May 2018 01:23:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527582209; cv=none; d=google.com; s=arc-20160816; b=xt/8CptKtoIwA67OzixV+uvMCE1JsiKXCfs+y68N7L2jrUcg9KtA488zRNzNvxMw8k cfGwR6rl1Qbb7eDkrn+x/mJL9LnEMKVbGvioIezSRpBjLo7kwwQ15IDCu33xhdhfz5DF gf8t0bhAQBPzh0R1/Lrge5C0M1dgczZrnKxzFf/24G4E8xywQ+QZDxHtSDDMfi2fDqtM mSyR3Y8cOjo8f0f6m6KT0OXKRsSuUcRhGPPtItGk/nPy0Rs5d+bglQwenHDS+Oe7ZxnH aXbWRKdUpF7dzBssVIF1i9J19xf5K3L0UiXufWYx6USztdsUJ9SQrkJA/7JupxDMNfN7 VTjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Ebwkh5by50d00zeycbPBBGAYC3mxpTU6o6gvs7tuUsA=; b=OiAhCPdZC9pnoan1BnyTxETV2cN5Octql/9WkZwLrnYFIpZwEUcmcExS7YPqN/vAFP AL2Ys25lcDsXMj/86/gu9VgvsYQLuKq5XXe0k6s9ojGRRIPX1k85yPYE4UOTyZCI6TqR 4FLj0O5N03Qd2wEp5YQVqJh5EVLa321BgkFlXLkonN5aaxjHzagmE9eGSG0ess8M93fQ 7jsY1U7ZZR01WlRAavQdUK/HmU18LzwxCvCs6R2WpnuwSO1utTD2x+wFrA/buD3j+YHk NOSpZbl9IYDVbqJ5w2HlbEsx8bCHSEdV8DfFggZ+Cti7VmFavsFQTTLmLyo3pKcK7ZD4 NrGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bc7-v6si31665595plb.310.2018.05.29.01.23.15; Tue, 29 May 2018 01:23:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932288AbeE2IVg (ORCPT + 99 others); Tue, 29 May 2018 04:21:36 -0400 Received: from mx2.suse.de ([195.135.220.15]:46005 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932081AbeE2IVc (ORCPT ); Tue, 29 May 2018 04:21:32 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 8EAADAF7F; Tue, 29 May 2018 08:21:30 +0000 (UTC) Date: Tue, 29 May 2018 10:21:30 +0200 From: Michal Hocko To: Randy Dunlap Cc: Mike Rapoport , Dave Chinner , Jonathan Corbet , LKML , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, "Darrick J. Wong" , David Sterba Subject: Re: [PATCH] doc: document scope NOFS, NOIO APIs Message-ID: <20180529082130.GO27180@dhcp22.suse.cz> References: <20180424183536.GF30619@thunk.org> <20180524114341.1101-1-mhocko@kernel.org> <20180524221715.GY10363@dastard> <20180525081624.GH11881@dhcp22.suse.cz> <20180527124721.GA4522@rapoport-lnx> <20180528092138.GI1517@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 28-05-18 09:10:43, Randy Dunlap wrote: > On 05/28/2018 02:21 AM, Michal Hocko wrote: [...] > > +reclaim context or when a transaction context nesting would be possible > > +via reclaim. The corresponding restore function when the critical > > "The corresponding restore ... ends." << That is not a complete sentence. > It's missing something. Dave has pointed that out. "The restore function should be called when the critical section ends." > > +section ends. All that ideally along with an explanation what is > > +the reclaim context for easier maintenance. > > + > > +Please note that the proper pairing of save/restore function allows > > +nesting so it is safe to call ``memalloc_noio_save`` respectively > > +``memalloc_noio_restore`` from an existing NOIO or NOFS scope. > > Please note that the proper pairing of save/restore functions allows > nesting so it is safe to call ``memalloc_noio_save`` or > ``memalloc_noio_restore`` respectively from an existing NOIO or NOFS scope. Fixed. Thanks -- Michal Hocko SUSE Labs