Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	david@fromorbit.com, linux-kernel@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	Theodore Ts'o <tytso@mit.edu>
Subject: Re: [GIT PULL] vfs: improve DAX behavior for 5.8, part 1
Date: Tue, 2 Jun 2020 16:53:05 -0700	[thread overview]
Message-ID: <20200602235305.GI1505637@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20200602165852.GB8230@magnolia>

On Tue, Jun 02, 2020 at 09:58:52AM -0700, Darrick J. Wong wrote:
> Hi Linus,
> 
> After many years of LKML-wrangling about how to enable programs to query
> and influence the file data access mode (DAX) when a filesystem resides
> on storage devices such as persistent memory, Ira Weiny has emerged with
> a proposed set of standard behaviors that has not been shot down by
> anyone!  We're more or less standardizing on the current XFS behavior
> and adapting ext4 to do the same.

Also, for those interested: The corresponding man page change mentioned in the
commit has been submitted here:

https://lore.kernel.org/lkml/20200505002016.1085071-1-ira.weiny@intel.com/

Ira

> 
> This pull request is the first of a handful that will make ext4 and XFS
> present a consistent interface for user programs that care about DAX.
> We add a statx attribute that programs can check to see if DAX is
> enabled on a particular file.  Then, we update the DAX documentation to
> spell out the user-visible behaviors that filesystems will guarantee
> (until the next storage industry shakeup).  The on-disk inode flag has
> been in XFS for a few years now.
> 
> Note that Stephen Rothwell reported a minor merge conflict[1] between
> the first cleanup patch and a different change in the block layer.  The
> resolution looks pretty straightforward, but let me know if you
> encounter problems.
> 
> --D
> 
> [1] https://lore.kernel.org/linux-next/20200522145848.38cdcf54@canb.auug.org.au/
> 
> The following changes since commit 0e698dfa282211e414076f9dc7e83c1c288314fd:
> 
>   Linux 5.7-rc4 (2020-05-03 14:56:04 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/vfs-5.8-merge-1
> 
> for you to fetch changes up to 83d9088659e8f113741bb197324bd9554d159657:
> 
>   Documentation/dax: Update Usage section (2020-05-04 08:49:39 -0700)
> 
> ----------------------------------------------------------------
> New code for 5.8:
> - Clean up io_is_direct.
> - Add a new statx flag to indicate when file data access is being done
>   via DAX (as opposed to the page cache).
> - Update the documentation for how system administrators and application
>   programmers can take advantage of the (still experimental DAX) feature.
> 
> ----------------------------------------------------------------
> Ira Weiny (3):
>       fs: Remove unneeded IS_DAX() check in io_is_direct()
>       fs/stat: Define DAX statx attribute
>       Documentation/dax: Update Usage section
> 
>  Documentation/filesystems/dax.txt | 142 +++++++++++++++++++++++++++++++++++++-
>  drivers/block/loop.c              |   6 +-
>  fs/stat.c                         |   3 +
>  include/linux/fs.h                |   7 +-
>  include/uapi/linux/stat.h         |   1 +
>  5 files changed, 147 insertions(+), 12 deletions(-)

  reply	other threads:[~2020-06-02 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 16:58 [GIT PULL] vfs: improve DAX behavior for 5.8, part 1 Darrick J. Wong
2020-06-02 23:53 ` Ira Weiny [this message]
2020-06-03  3:50 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200602235305.GI1505637@iweiny-DESK2.sc.intel.com \
    --to=ira.weiny@intel.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox