From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2767C169C4 for ; Fri, 8 Feb 2019 09:02:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9A6DA21916 for ; Fri, 8 Feb 2019 09:02:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727384AbfBHJCs (ORCPT ); Fri, 8 Feb 2019 04:02:48 -0500 Received: from mx2.suse.de ([195.135.220.15]:39254 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726115AbfBHJCs (ORCPT ); Fri, 8 Feb 2019 04:02:48 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 83E2BAE30; Fri, 8 Feb 2019 09:02:46 +0000 (UTC) Date: Fri, 8 Feb 2019 10:02:45 +0100 From: Johannes Thumshirn To: "Kani, Toshi" Cc: "dan.j.williams@intel.com" , "lsf-pc@lists.linux-foundation.org" , "linux-xfs@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" Subject: Re: [LSF/MM TOPIC] The end of the DAX experiment Message-ID: <20190208090245.GA8038@linux-x5ow.site> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On 07/02/2019 22:51, Kani, Toshi wrote: > I've also had multiple users complained about 'mount -o dax' succeeded > by falling back to non-dax despite of their intent. Such users wasted > many hours without knowing their setup error / current restrictions. > The next think they always ask is how to check if dax is enabled in such > case, and they are not happy about limited interfaces (ex. look for > mount entry in /proc/mounts), either. Exactly, there's a need for admins and user-space applications to check if they can use DAX or not. See also [1] for reference. > Same as above. Such enhancement should be possible after EXPERIMENTAL > is removed from 'mount -o dax'. IOW, a separate EXPERIMENTAL message > can be shown when user requests per-directory dax. Just as a data point here, in our Kernels we've removed the EXPERIMENTAL warning for DAX on XFS (but not EXT4) and we are supporting it for some limited use-cases. [1] https://lore.kernel.org/linux-fsdevel/20181002100531.GC4135@quack2.suse.cz/ Byte, Johannes -- Johannes Thumshirn SUSE Labs Filesystems jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 777C1211BFCC5 for ; Fri, 8 Feb 2019 01:02:48 -0800 (PST) Date: Fri, 8 Feb 2019 10:02:45 +0100 From: Johannes Thumshirn Subject: Re: [LSF/MM TOPIC] The end of the DAX experiment Message-ID: <20190208090245.GA8038@linux-x5ow.site> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: "Kani, Toshi" Cc: "linux-ext4@vger.kernel.org" , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , "linux-xfs@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "lsf-pc@lists.linux-foundation.org" List-ID: On 07/02/2019 22:51, Kani, Toshi wrote: > I've also had multiple users complained about 'mount -o dax' succeeded > by falling back to non-dax despite of their intent. Such users wasted > many hours without knowing their setup error / current restrictions. > The next think they always ask is how to check if dax is enabled in such > case, and they are not happy about limited interfaces (ex. look for > mount entry in /proc/mounts), either. Exactly, there's a need for admins and user-space applications to check if = they can use DAX or not. See also [1] for reference. > Same as above. Such enhancement should be possible after EXPERIMENTAL > is removed from 'mount -o dax'. IOW, a separate EXPERIMENTAL message > can be shown when user requests per-directory dax. Just as a data point here, in our Kernels we've removed the EXPERIMENTAL warning for DAX on XFS (but not EXT4) and we are supporting it for some lim= ited use-cases. [1] https://lore.kernel.org/linux-fsdevel/20181002100531.GC4135@quack2.suse= .cz/ Byte, Johannes -- = Johannes Thumshirn SUSE Labs Filesystems jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N=FCrnberg GF: Felix Imend=F6rffer, Jane Smithard, Graham Norton HRB 21284 (AG N=FCrnberg) Key fingerprint =3D EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm