From: Johannes Thumshirn <jthumshirn@suse.de>
To: "Kani, Toshi" <toshi.kani@hpe.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [LSF/MM TOPIC] The end of the DAX experiment
Date: Fri, 8 Feb 2019 10:02:45 +0100 [thread overview]
Message-ID: <20190208090245.GA8038@linux-x5ow.site> (raw)
In-Reply-To: <d7790ae27161db2fcf0b10a7d5d67de833f2d3fe.camel@hpe.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
To: "Kani, Toshi" <toshi.kani@hpe.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] The end of the DAX experiment
Date: Fri, 8 Feb 2019 10:02:45 +0100 [thread overview]
Message-ID: <20190208090245.GA8038@linux-x5ow.site> (raw)
In-Reply-To: <d7790ae27161db2fcf0b10a7d5d67de833f2d3fe.camel@hpe.com>
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
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2019-02-08 9:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 21:12 [LSF/MM TOPIC] The end of the DAX experiment Dan Williams
2019-02-06 21:12 ` Dan Williams
2019-02-07 21:51 ` Kani, Toshi
2019-02-07 21:51 ` Kani, Toshi
2019-02-08 9:02 ` Johannes Thumshirn [this message]
2019-02-08 9:02 ` Johannes Thumshirn
2019-02-14 13:46 ` [Lsf-pc] " Michal Hocko
2019-02-14 13:46 ` Michal Hocko
2019-02-14 18:25 ` Dan Williams
2019-02-14 18:25 ` Dan Williams
2019-02-14 19:10 ` Jerome Glisse
2019-02-14 19:10 ` Jerome Glisse
2019-02-14 19:31 ` Dan Williams
2019-02-14 19:31 ` Dan Williams
2019-02-14 20:08 ` Matthew Wilcox
2019-02-14 20:08 ` Matthew Wilcox
2019-02-14 20:20 ` Dan Williams
2019-02-14 20:20 ` Dan Williams
2019-02-14 20:34 ` Jerome Glisse
2019-02-14 20:34 ` Jerome Glisse
2019-02-16 5:37 ` Dave Chinner
2019-02-16 5:37 ` Dave Chinner
2019-06-05 16:22 ` Goldwyn Rodrigues
2019-06-05 16:22 ` Goldwyn Rodrigues
2019-06-07 6:00 ` Dan Williams
2019-06-07 6:00 ` Dan Williams
2019-12-09 16:20 ` Boaz Harrosh
2019-12-09 16:20 ` Boaz Harrosh
2019-02-17 20:29 ` Ric Wheeler
2019-02-17 20:29 ` Ric Wheeler
2019-02-18 18:17 ` Dan Williams
2019-02-18 18:17 ` Dan Williams
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=20190208090245.GA8038@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=toshi.kani@hpe.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.