Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp481531pxu; Tue, 5 Jan 2021 17:18:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJxHFSt2QLVV+rNOaJPsPI528bQ3fSueupY5Ukea5iP9DLEug9fkiWrI9jRZ3zrcDDPrp+Fp X-Received: by 2002:a50:bacb:: with SMTP id x69mr2274388ede.39.1609895912604; Tue, 05 Jan 2021 17:18:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609895912; cv=none; d=google.com; s=arc-20160816; b=ZY9QZBRNwfduntts2S4UgiKfcGM+B4rIWSTd8hyKwpf+ewWMJalAzxvf+8tNq9wI3V gSUgetV2uT1SiHp8ID7aRWznD8vV2/ne96oesNAS4SV5IkTfgKl/ILk7q2rCwQECVBh1 VhDr057Y7d6HgTYQLnptVfOHN5skH7ATUFVnofFsS9/T7mNYM3Lhm5LLV8wbN+ig4KRC /3Fmw/yjvNk13E83E19j0Z3IJL7D412bC194kbCzc+ZKIqMKaCf5mhqU2sRJ8iQP9FSN pGEs9CentyP534nxnRD3UbFE6Y050wu7yXHFpsfafAKn68fR6kkoCxScsoCgVQdFUROT hFmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=KRwct9Eot7TX/DgKLd4/HsrrBjdkDvs6xcVGOAoZFEw=; b=FN3PTj88w/CA1z/wqHko2omQ90D3kBhNBz7J8fVClQ/3Sz9HtA+7TI6KDpoYx/GycM kBImRNIwGQmD8sJSP8qVMA2eZbp1tX2kDySpGNcX3zXRqpBcr8NPu6t6bnHqjDXuuvea 6LG0AX0gnMgRzfsei5niDjWoUAhgLSBT1a1T5F5zy7POISUCz2y6ZJRO1jKn6hv7viAH lUraMnRu6rkwKWM9UXF8J4GAa3uFmjUDrZg+nuG2iGDZmAw1pbd+CvY99kRaLJTSUrgz ClX3D7Tv+RdknHg5TE+9yGV1nnE8LSn5iILhnKH9TxoKr5W0TrvgthPeiZQxBMJA9LuG 2ZEQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id kt26si316303ejb.443.2021.01.05.17.18.08; Tue, 05 Jan 2021 17:18:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726133AbhAFBQv (ORCPT + 99 others); Tue, 5 Jan 2021 20:16:51 -0500 Received: from mail.cn.fujitsu.com ([183.91.158.132]:9310 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725843AbhAFBQu (ORCPT ); Tue, 5 Jan 2021 20:16:50 -0500 X-IronPort-AV: E=Sophos;i="5.78,478,1599494400"; d="scan'208";a="103219147" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 06 Jan 2021 09:16:01 +0800 Received: from G08CNEXMBPEKD04.g08.fujitsu.local (unknown [10.167.33.201]) by cn.fujitsu.com (Postfix) with ESMTP id 71F5B4CE6D6F; Wed, 6 Jan 2021 09:15:55 +0800 (CST) Received: from [10.167.225.206] (10.167.225.206) by G08CNEXMBPEKD04.g08.fujitsu.local (10.167.33.201) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 6 Jan 2021 09:15:54 +0800 Subject: Re: [PATCH] Documentation/dax: Update description of DAX policy changing To: Ira Weiny CC: , , , , , , , References: <20210104024040.5381-1-lihao2018.fnst@cn.fujitsu.com> <20210104163653.GG3097896@iweiny-DESK2.sc.intel.com> From: "Li, Hao" Message-ID: <1a4dc84b-56ee-bf77-cf0d-dd9e0637b90c@cn.fujitsu.com> Date: Wed, 6 Jan 2021 09:15:53 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210104163653.GG3097896@iweiny-DESK2.sc.intel.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Language: en-US X-Originating-IP: [10.167.225.206] X-ClientProxiedBy: G08CNEXCHPEKD06.g08.fujitsu.local (10.167.33.205) To G08CNEXMBPEKD04.g08.fujitsu.local (10.167.33.201) X-yoursite-MailScanner-ID: 71F5B4CE6D6F.AFE1B X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: lihao2018.fnst@cn.fujitsu.com X-Spam-Status: No Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/1/5 0:36, Ira Weiny wrote: > On Mon, Jan 04, 2021 at 10:40:40AM +0800, Hao Li wrote: >> After commit 77573fa310d9 ("fs: Kill DCACHE_DONTCACHE dentry even if >> DCACHE_REFERENCED is set"), changes to DAX policy will take effect >> as soon as all references to this file are gone. >> >> Update the documentation accordingly. >> >> Signed-off-by: Hao Li >> --- >>  Documentation/filesystems/dax.txt | 15 ++------------- >>  1 file changed, 2 insertions(+), 13 deletions(-) >> >> diff --git a/Documentation/filesystems/dax.txt b/Documentation/filesystems/dax.txt >> index 8fdb78f3c6c9..a5af22831087 100644 >> --- a/Documentation/filesystems/dax.txt >> +++ b/Documentation/filesystems/dax.txt >> @@ -84,19 +84,8 @@ Summary >>         described in 6) below. >>   >>   6. When changing the S_DAX policy via toggling the persistent FS_XFLAG_DAX flag, >                                                                                   ^^ >                                                   I would delete this '.' as well. > >> -    the change in behaviour for existing regular files may not occur >> -    immediately.  If the change must take effect immediately, the administrator >> -    needs to: >> - >> -    a) stop the application so there are no active references to the data set >> -       the policy change will affect >> - >> -    b) evict the data set from kernel caches so it will be re-instantiated when >> -       the application is restarted. This can be achieved by: >> - >> -       i. drop-caches >> -       ii. a filesystem unmount and mount cycle >> -       iii. a system reboot >> +    the change to existing regular file won't take effect until the file is closed >                                                                       ^^^^^ >                                                                       files > >> +    by all processes or all processes referencing the file are stopped. > > So how about: > >    6. When changing the S_DAX policy via toggling the persistent FS_XFLAG_DAX >       flag the change to existing regular files won't take effect until the file >       is closed by all processes or all processes referencing the file are >       stopped. > > I also feel like mentioning the stoppage of process' is redundant as users > should know that will result in the closing of those FDs but I'm ok leaving it > if others like it. Thanks, it's much better than before. Regards, Hao Li > > > Ira > >>   >>   >>  Details >> -- >> 2.29.2 >> >> >> > >