linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Jan Kara <jack@suse.cz>
Cc: Ira Weiny <ira.weiny@intel.com>, <linux-ext4@vger.kernel.org>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	"Theodore Y. Ts'o" <tytso@mit.edu>,
	Eric Biggers <ebiggers@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Dan Williams <dan.j.williams@intel.com>,
	Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@lst.de>, Jeff Moyer <jmoyer@redhat.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 6/8] fs/ext4: Make DAX mount option a tri-state
Date: Tue, 2 Jun 2020 09:16:33 +0800	[thread overview]
Message-ID: <5ED5A871.4070101@cn.fujitsu.com> (raw)
In-Reply-To: <20200528094144.GD14550@quack2.suse.cz>

On 2020/5/28 17:41, Jan Kara wrote:
> On Thu 28-05-20 16:56:51, Xiao Yang wrote:
>> On 2020/5/28 7:50, Ira Weiny wrote:
>>> On Wed, May 27, 2020 at 01:54:54PM +0800, Xiao Yang wrote:
>>>> On 2020/5/22 3:13, ira.weiny@intel.com wrote:
>>>>> From: Ira Weiny<ira.weiny@intel.com>
>>>>>
>>>>> We add 'always', 'never', and 'inode' (default).  '-o dax' continues to
>>>>> operate the same which is equivalent to 'always'.  This new
>>>>> functionality is limited to ext4 only.
>>>>>
>>>>> Specifically we introduce a 2nd DAX mount flag EXT4_MOUNT2_DAX_NEVER and set
>>>>> it and EXT4_MOUNT_DAX_ALWAYS appropriately for the mode.
>>>>>
>>>>> We also force EXT4_MOUNT2_DAX_NEVER if !CONFIG_FS_DAX.
>>>>>
>>>>> Finally, EXT4_MOUNT2_DAX_INODE is used solely to detect if the user
>>>>> specified that option for printing.
>>>> Hi Ira,
>>>>
>>>> I have two questions when reviewing this patch:
>>>> 1) After doing mount with the same dax=inode option, ext4/xfs shows
>>>> differnt output(i.e. xfs doesn't print 'dax=inode'):
>>>> ---------------------------------------------------
>>>> # mount -o dax=inode /dev/pmem0 /mnt/xfstests/test/
>>>> # mount | grep pmem0
>>>> /dev/pmem0 on /mnt/xfstests/test type ext4 (rw,relatime,seclabel,dax=inode)
>>>>
>>>> # mount -odax=inode /dev/pmem1 /mnt/xfstests/scratch/
>>>> # mount | grep pmem1
>>>> /dev/pmem1 on /mnt/xfstests/scratch type xfs
>>>> (rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota)
>>>> ----------------------------------------------------
>>>> Is this expected output? why don't unify the output?
>>>
>>> Correct. dax=inode is the default.  xfs treats that default the same whether
>>> you specify it on the command line or not.
>>>
>>> For ext4 Jan specifically asked that if the user specified dax=inode on the
>>> command line that it be printed on the mount options.  If you don't specify
>>> anything then dax=inode is in effect but ext4 will not print anything.
>>>
>>> I had the behavior the same as XFS originally but Jan wanted it this way.  The
>>> XFS behavior is IMO better and is what the new mount infrastructure gives by
>>> default.
>>
>> Could we unify the output?  It is strange for me to use differnt output on
>> ext4 and xfs.
>
> If we'd unify the output with XFS, it would be inconsistent with all the
> other ext4 mount options. So I disagree with that. I agree it is not ideal
> to have different behavior between xfs and ext4 but such is the historical
> behavior. If we want to change that, we need to change the handling for all
> the ext4 mount options. I'm open for that discussion but it is a problem
> unrelated to this patch set.
Hi Jan,

Thanks for your quick feedback.
Of course, this doubt should not block the patch set.

Best Regards,
Xiao Yang
>
> 								Honza




  reply	other threads:[~2020-06-02  1:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 19:13 [PATCH V4 0/8] Enable ext4 support for per-file/directory DAX operations ira.weiny
2020-05-21 19:13 ` [PATCH V4 1/8] fs/ext4: Narrow scope of DAX check in setflags ira.weiny
2020-05-22  7:58   ` Jan Kara
2020-05-21 19:13 ` [PATCH V4 2/8] fs/ext4: Disallow verity if inode is DAX ira.weiny
2020-05-21 19:13 ` [PATCH V4 3/8] fs/ext4: Change EXT4_MOUNT_DAX to EXT4_MOUNT_DAX_ALWAYS ira.weiny
2020-05-21 19:13 ` [PATCH V4 4/8] fs/ext4: Update ext4_should_use_dax() ira.weiny
2020-05-22 10:41   ` Jan Kara
2020-05-21 19:13 ` [PATCH V4 5/8] fs/ext4: Only change S_DAX on inode load ira.weiny
2020-05-21 19:13 ` [PATCH V4 6/8] fs/ext4: Make DAX mount option a tri-state ira.weiny
2020-05-27  5:54   ` Xiao Yang
2020-05-27 23:50     ` Ira Weiny
2020-05-28  8:56       ` Xiao Yang
2020-05-28  9:41         ` Jan Kara
2020-06-02  1:16           ` Xiao Yang [this message]
2020-05-21 19:13 ` [PATCH V4 7/8] fs/ext4: Introduce DAX inode flag ira.weiny
2020-05-22 11:48   ` Jan Kara
2020-05-25  4:39     ` Ira Weiny
2020-05-25  7:28       ` Jan Kara
2020-05-23  5:13   ` Andreas Dilger
2020-05-21 19:13 ` [PATCH V4 8/8] Documentation/dax: Update DAX enablement for ext4 ira.weiny

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=5ED5A871.4070101@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=dan.j.williams@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=ira.weiny@intel.com \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).