From patchwork Mon Apr 13 05:40:37 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ira Weiny X-Patchwork-Id: 11485027 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 5F93E912 for ; Mon, 13 Apr 2020 05:42:11 +0000 (UTC) Received: from vger.kernel.org (unknown [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 42C552073E for ; Mon, 13 Apr 2020 05:42:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 42C552073E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-xfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727908AbgDMFlP (ORCPT ); Mon, 13 Apr 2020 01:41:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.18]:42622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727818AbgDMFlP (ORCPT ); Mon, 13 Apr 2020 01:41:15 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2C286C008675; Sun, 12 Apr 2020 22:41:14 -0700 (PDT) IronPort-SDR: 3tsMuENpoNaAKHQjs/P76BQHTKe/DcDwOeL6Zh2RADaTOwHGwtjLj5gamAXSOjGaBEpRlgHLT2 GnKuhfRoaqNQ== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Apr 2020 22:41:13 -0700 IronPort-SDR: smLHDgW+pkdPq/kpAoSP44TxzQBWYSseu3XYsoeNR/b4htd4C2u2RWptdfP3C/oN/y7bBwVltC ZgvuHt1npwlw== X-IronPort-AV: E=Sophos;i="5.72,377,1580803200"; d="scan'208";a="453049728" Received: from iweiny-desk2.sc.intel.com (HELO localhost) ([10.3.52.147]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Apr 2020 22:41:13 -0700 From: ira.weiny@intel.com To: linux-kernel@vger.kernel.org, "Darrick J. Wong" Cc: Ira Weiny , Dan Williams , Dave Chinner , Christoph Hellwig , "Theodore Y. Ts'o" , Jan Kara , linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jeff Moyer Subject: [PATCH V7 0/9] Enable per-file/per-directory DAX operations V7 Date: Sun, 12 Apr 2020 22:40:37 -0700 Message-Id: <20200413054046.1560106-1-ira.weiny@intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org From: Ira Weiny Changes from V6: Incorporate feedback on patches Add ability to change FS_XFLAG_DAX on files at any time. Add a don't cache flag to the VFS layer Preserve internal XFS IDONTCACHE behavior for bulkstat operations At LSF/MM'19 [1] [2] we discussed applications that overestimate memory consumption due to their inability to detect whether the kernel will instantiate page cache for a file, and cases where a global dax enable via a mount option is too coarse. The following patch series enables the use of DAX on individual files and/or directories on xfs, and lays some groundwork to do so in ext4. It further enhances the dax mount option to be a tri-state of 'always', 'never', or 'iflag' (default). Furthermore, it maintians '-o dax' to be equivalent to '-o dax=always'. The insight at LSF/MM was to separate the per-mount or per-file "physical" (FS_XFLAG_DAX) capability switch from an "effective" (S_DAX) attribute for the file. At LSF/MM we discussed the difficulties of switching the DAX state of a file with active mappings / page cache. It was thought the races could be avoided by limiting DAX state flips to 0-length files. However, this turns out to not be true.[3][5] This is because address space operations (a_ops) may be in use at any time the inode is referenced. For this reason direct manipulation of the FS_XFLAG_DAX is allowed but the operation of the file (S_DAX) is not immediately changed. Details of when and how DAX state can be changed on a file is included in a documentation patch. It should be noted that FS_XFLAG_DAX inheritance is not shown in this patch set as it was maintained from previous work on XFS. FS_XFLAG_DAX and it's inheritance will need to be added to other file systems for user control. [1] https://lwn.net/Articles/787973/ [2] https://lwn.net/Articles/787233/ [3] https://lkml.org/lkml/2019/10/20/96 [4] https://patchwork.kernel.org/patch/11310511/ [5] https://lore.kernel.org/lkml/20200405061945.GA94792@iweiny-DESK2.sc.intel.com/ To: linux-kernel@vger.kernel.org Cc: "Darrick J. Wong" Cc: Dan Williams Cc: Dave Chinner Cc: Christoph Hellwig Cc: "Theodore Y. Ts'o" Cc: Jan Kara Cc: linux-ext4@vger.kernel.org Cc: linux-xfs@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org Changes from V5: * make dax mount option a tri-state * Reject changes to FS_XFLAG_DAX for regular files - Allow only on directories * Update documentation Changes from V4: * Open code the aops lock rather than add it to the xfs_ilock() subsystem (Darrick's comments were obsoleted by this change) * Fix lkp build suggestions and bugs Changes from V3: * Remove global locking... :-D * put back per inode locking and remove pre-mature optimizations * Fix issues with Directories having IS_DAX() set * Fix kernel crash issues reported by Jeff * Add some clean up patches * Consolidate diflags to iflags functions * Update/add documentation * Reorder/rename patches quite a bit Changes from V2: * Move i_dax_sem to be a global percpu_rw_sem rather than per inode Internal discussions with Dan determined this would be easier, just as performant, and slightly less overhead that having it in the SB as suggested by Jan * Fix locking order in comments and throughout code * Change "mode" to "state" throughout commits * Add CONFIG_FS_DAX wrapper to disable inode_[un]lock_state() when not configured * Add static branch for which is activated by a device which supports DAX in XFS * Change "lock/unlock" to up/down read/write as appropriate Previous names were over simplified * Update comments/documentation * Remove the xfs specific lock to the vfs (global) layer. * Fix i_dax_sem locking order and comments * Move 'i_mapped' count from struct inode to struct address_space and rename it to mmap_count * Add inode_has_mappings() call * Fix build issues * Clean up syntax spacing and minor issues * Update man page text for STATX_ATTR_DAX * Add reviewed-by's * Rebase to 5.6 Rename patch: from: fs/xfs: Add lock/unlock state to xfs to: fs/xfs: Add write DAX lock to xfs layer Add patch: fs/xfs: Clarify lockdep dependency for xfs_isilocked() Drop patch: fs/xfs: Fix truncate up Ira Weiny (9): fs/xfs: Remove unnecessary initialization of i_rwsem fs: Remove unneeded IS_DAX() check in io_is_direct() fs/stat: Define DAX statx attribute fs/xfs: Make DAX mount option a tri-state fs/xfs: Create function xfs_inode_enable_dax() fs/xfs: Combine xfs_diflags_to_linux() and xfs_diflags_to_iflags() fs: Define I_DONTCACNE in VFS layer fs/xfs: Change xfs_ioctl_setattr_dax_invalidate() Documentation/dax: Update Usage section Documentation/filesystems/dax.txt | 166 +++++++++++++++++++++++++++++- drivers/block/loop.c | 6 +- fs/stat.c | 3 + fs/xfs/xfs_icache.c | 4 +- fs/xfs/xfs_inode.h | 1 + fs/xfs/xfs_ioctl.c | 135 +++--------------------- fs/xfs/xfs_iops.c | 74 ++++++++----- fs/xfs/xfs_mount.h | 3 +- fs/xfs/xfs_super.c | 44 +++++++- include/linux/fs.h | 13 ++- include/uapi/linux/stat.h | 1 + 11 files changed, 288 insertions(+), 162 deletions(-)