Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp8058522ybl; Thu, 16 Jan 2020 09:55:55 -0800 (PST) X-Google-Smtp-Source: APXvYqz10NoA5K3hhTpAGdryPOtDmJY8RmAIe/383tZCu8FkqIXUgWJaN3I/dMxNvFh0nz5At8Wc X-Received: by 2002:a05:6830:18ce:: with SMTP id v14mr2970820ote.36.1579197355474; Thu, 16 Jan 2020 09:55:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579197355; cv=none; d=google.com; s=arc-20160816; b=sdMrfHJbg0YtUk0eY2ahTVIEvQ2Zb6+Vpp8aellyAniA/SoBbk/M+WA6JqdMFLwWNy 0sSlTcFZRh7mhbgh84CJjRHerYf8MFxuU3l6SmdHatyNT7qxyJ5VB39y28ZmUVByuQ72 HvOOmwkI1w5eALYPKZOA0/wzisY97VHp2bxcSs9zbSVKODd6XZ2BH2wEdO9iYXTwDu2e sm0gQdu4AguIKtmg9wDouBoqU4WdGR3p3uwIw5+lsTfb9qPxeV79TeJkjnNzgn7xiD/Q jk6x3KJfjRir1US8xwTH9Nx1jhl60jyfMapPDNUbalJbv1QLhvkP8TFrm8AeF+WEM01E krzw== 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; bh=G0DD0rUpEH3Hm243sqQoHqX/taAr9AnlgAZ5gW6U8rI=; b=Ri5/DXA3tNoD8s25+Hcy78+UO34o45WHQ81F1EBHu8BnO5tZDNEd/1SgyjK1x7TUuF Dv4xU1QqvLHLSfW8WF70oGCuu7IxhHWlo0zTnRfySy0IahgmZQ5+fw1i4lgxSBm8wwhh X0+qdlwCtPIBHO9bQ0L9TcFriGt29nj8OMtwjIz4iWcvlv/hBJa/5y6O8ziqWvPu+Y72 78i5AAUUSmCejkWNcJ+30dwQaM8dhToiWdFGHH4x+eeWgFr2hsfkrvfMkVAtqwMHsGaV +tnQSFz3DeXn29urexcJLlp4RVi7A7bOL7ZGalhWUSjp2ypB6fKt3+SkkkugrxOwI5NB qEDg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b10si11886359oic.153.2020.01.16.09.55.44; Thu, 16 Jan 2020 09:55:55 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388936AbgAPRzG (ORCPT + 99 others); Thu, 16 Jan 2020 12:55:06 -0500 Received: from mga06.intel.com ([134.134.136.31]:13777 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2406025AbgAPRzF (ORCPT ); Thu, 16 Jan 2020 12:55:05 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2020 09:55:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,327,1574150400"; d="scan'208";a="214168129" Received: from iweiny-desk2.sc.intel.com ([10.3.52.157]) by orsmga007.jf.intel.com with ESMTP; 16 Jan 2020 09:55:02 -0800 Date: Thu, 16 Jan 2020 09:55:02 -0800 From: Ira Weiny To: "Darrick J. Wong" Cc: Dan Williams , Jan Kara , Linux Kernel Mailing List , Alexander Viro , Dave Chinner , Christoph Hellwig , "Theodore Y. Ts'o" , linux-ext4 , linux-xfs , linux-fsdevel Subject: Re: [RFC PATCH V2 01/12] fs/stat: Define DAX statx attribute Message-ID: <20200116175501.GC24522@iweiny-DESK2.sc.intel.com> References: <20200110192942.25021-1-ira.weiny@intel.com> <20200110192942.25021-2-ira.weiny@intel.com> <20200115113715.GB2595@quack2.suse.cz> <20200115173834.GD8247@magnolia> <20200115194512.GF23311@iweiny-DESK2.sc.intel.com> <20200115223821.GG23311@iweiny-DESK2.sc.intel.com> <20200116053935.GB8235@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200116053935.GB8235@magnolia> User-Agent: Mutt/1.11.1 (2018-12-01) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Wed, Jan 15, 2020 at 09:39:35PM -0800, Darrick J. Wong wrote: > On Wed, Jan 15, 2020 at 02:38:21PM -0800, Ira Weiny wrote: > > On Wed, Jan 15, 2020 at 12:10:50PM -0800, Dan Williams wrote: > > > On Wed, Jan 15, 2020 at 11:45 AM Ira Weiny wrote: > > > > > > > > On Wed, Jan 15, 2020 at 09:38:34AM -0800, Darrick J. Wong wrote: > > > > > On Wed, Jan 15, 2020 at 12:37:15PM +0100, Jan Kara wrote: > > > > > > On Fri 10-01-20 11:29:31, ira.weiny@intel.com wrote: > > > > > > > From: Ira Weiny > > > > > > > > > [snip] > > > > Sure, but for now I think referencing mmap for details on MAP_SYNC works. > > > > I suspect that we may have some word smithing once I get this series in and we > > submit a change to the statx man page itself. Can I move forward with the > > following for this patch? > > > > > > STATX_ATTR_DAX > > > > The file is in the DAX (cpu direct access) state. DAX state > > Hmm, now that I see it written out, I kind of like "DAX mode" > better now. :/ > > "The file is in DAX (CPU direct access) mode. DAX mode attempts..." Sure... now you tell me... ;-) Seriously, we could use mode here in the man page as this is less confusing to say "DAX mode". But I think the code should still use 'state' because mode is just too overloaded. You were not the only one who was thrown by my use of mode and I don't want that confusion when we look at this code 2 weeks from now... https://www.reddit.com/r/ProgrammerHumor/comments/852og2/only_god_knows/ ;-) > > > attempts to minimize software cache effects for both I/O and > > memory mappings of this file. It requires a file system which > > has been configured to support DAX. > > > > DAX generally assumes all accesses are via cpu load / store > > instructions which can minimize overhead for small accesses, but > > may adversely affect cpu utilization for large transfers. > > > > File I/O is done directly to/from user-space buffers and memory > > mapped I/O may be performed with direct memory mappings that > > bypass kernel page cache. > > > > While the DAX property tends to result in data being transferred > > synchronously, it does not give the same guarantees of > > synchronous I/O where data and the necessary metadata are > > transferred together. > > (I'm frankly not sure that synchronous I/O actually guarantees that the > metadata has hit stable storage...) I'll let you and Dan work this one out... ;-) Ira