From: Dave Chinner <david@fromorbit.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>, Jan Kara <jack@suse.cz>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
micah.parrish@hpe.com, Jens Axboe <axboe@fb.com>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH v3 2/5] block: Add bdev_supports_dax() for dax mount checks
Date: Tue, 10 May 2016 07:19:03 +1000 [thread overview]
Message-ID: <20160509211903.GW18496@dastard> (raw)
In-Reply-To: <CAPcyv4g6mPsmHM6OSTi78n_KBKCZrb1ou90=xWuhc7eGyx0DPg@mail.gmail.com>
On Mon, May 09, 2016 at 11:23:03AM -0700, Dan Williams wrote:
> On Mon, May 9, 2016 at 11:12 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > On Sun, 2016-05-08 at 12:14 -0700, Dan Williams wrote:
> >> On Thu, May 5, 2016 at 5:29 PM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > :
> >> > +int bdev_supports_dax(struct super_block *sb, int blocksize)
> >> > +{
> >> > + struct blk_dax_ctl dax = {
> >> > + .sector = 0,
> >> > + .size = PAGE_SIZE,
> >> > + };
> >> > + int err;
> >> > +
> >> > + if (blocksize != PAGE_SIZE) {
> >> > + vfs_msg(sb, KERN_ERR, "error: unsupported blocksize for
> >> > dax");
> >> > + return -EINVAL;
> >> > + }
> >> > +
> >> > + err = bdev_direct_access(sb->s_bdev, &dax);
> >> > + if (err < 0) {
> >> > + switch (err) {
> >> > + case -EOPNOTSUPP:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: device does not support dax");
> >> > + break;
> >> > + case -EINVAL:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: unaligned partition for dax");
> >> > + break;
> >> > + default:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: dax access failed (%d)", err);
> >> > + }
> >> > + return err;
> >> > + }
> >> > +
> >> > + return 0;
> >> > +}
> >> > +EXPORT_SYMBOL_GPL(bdev_supports_dax);
> >>
> >> This patch should replace blkdev_dax_capable(), or just reuse that
> >> existing routine, or am I missing something?
> >
> > Good question. bdev_supports_dax() is a helper function tailored for the
> > filesystem's mount -o dax case. While blkdev_dax_capable() is similar, it
> > does not need error messages like "device does not support dax" since it
> > implicitly enables dax when capable. So, I think we can keep
> > blkdev_dax_capable(), but change it to call bdev_direct_access() so that
> > actual check is performed in a single place.
>
> Sounds good to me.
Can you name them consistently then? i.e. blkdev_dax_supported() and
blkdev_dax_capable()?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Toshi Kani <toshi.kani@hpe.com>, Jan Kara <jack@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@infradead.org>,
Boaz Harrosh <boaz@plexistor.com>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
micah.parrish@hpe.com,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] block: Add bdev_supports_dax() for dax mount checks
Date: Tue, 10 May 2016 07:19:03 +1000 [thread overview]
Message-ID: <20160509211903.GW18496@dastard> (raw)
In-Reply-To: <CAPcyv4g6mPsmHM6OSTi78n_KBKCZrb1ou90=xWuhc7eGyx0DPg@mail.gmail.com>
On Mon, May 09, 2016 at 11:23:03AM -0700, Dan Williams wrote:
> On Mon, May 9, 2016 at 11:12 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > On Sun, 2016-05-08 at 12:14 -0700, Dan Williams wrote:
> >> On Thu, May 5, 2016 at 5:29 PM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > :
> >> > +int bdev_supports_dax(struct super_block *sb, int blocksize)
> >> > +{
> >> > + struct blk_dax_ctl dax = {
> >> > + .sector = 0,
> >> > + .size = PAGE_SIZE,
> >> > + };
> >> > + int err;
> >> > +
> >> > + if (blocksize != PAGE_SIZE) {
> >> > + vfs_msg(sb, KERN_ERR, "error: unsupported blocksize for
> >> > dax");
> >> > + return -EINVAL;
> >> > + }
> >> > +
> >> > + err = bdev_direct_access(sb->s_bdev, &dax);
> >> > + if (err < 0) {
> >> > + switch (err) {
> >> > + case -EOPNOTSUPP:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: device does not support dax");
> >> > + break;
> >> > + case -EINVAL:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: unaligned partition for dax");
> >> > + break;
> >> > + default:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: dax access failed (%d)", err);
> >> > + }
> >> > + return err;
> >> > + }
> >> > +
> >> > + return 0;
> >> > +}
> >> > +EXPORT_SYMBOL_GPL(bdev_supports_dax);
> >>
> >> This patch should replace blkdev_dax_capable(), or just reuse that
> >> existing routine, or am I missing something?
> >
> > Good question. bdev_supports_dax() is a helper function tailored for the
> > filesystem's mount -o dax case. While blkdev_dax_capable() is similar, it
> > does not need error messages like "device does not support dax" since it
> > implicitly enables dax when capable. So, I think we can keep
> > blkdev_dax_capable(), but change it to call bdev_direct_access() so that
> > actual check is performed in a single place.
>
> Sounds good to me.
Can you name them consistently then? i.e. blkdev_dax_supported() and
blkdev_dax_capable()?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Toshi Kani <toshi.kani@hpe.com>, Jan Kara <jack@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@infradead.org>,
Boaz Harrosh <boaz@plexistor.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
micah.parrish@hpe.com,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] block: Add bdev_supports_dax() for dax mount checks
Date: Tue, 10 May 2016 07:19:03 +1000 [thread overview]
Message-ID: <20160509211903.GW18496@dastard> (raw)
In-Reply-To: <CAPcyv4g6mPsmHM6OSTi78n_KBKCZrb1ou90=xWuhc7eGyx0DPg@mail.gmail.com>
On Mon, May 09, 2016 at 11:23:03AM -0700, Dan Williams wrote:
> On Mon, May 9, 2016 at 11:12 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > On Sun, 2016-05-08 at 12:14 -0700, Dan Williams wrote:
> >> On Thu, May 5, 2016 at 5:29 PM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > :
> >> > +int bdev_supports_dax(struct super_block *sb, int blocksize)
> >> > +{
> >> > + struct blk_dax_ctl dax = {
> >> > + .sector = 0,
> >> > + .size = PAGE_SIZE,
> >> > + };
> >> > + int err;
> >> > +
> >> > + if (blocksize != PAGE_SIZE) {
> >> > + vfs_msg(sb, KERN_ERR, "error: unsupported blocksize for
> >> > dax");
> >> > + return -EINVAL;
> >> > + }
> >> > +
> >> > + err = bdev_direct_access(sb->s_bdev, &dax);
> >> > + if (err < 0) {
> >> > + switch (err) {
> >> > + case -EOPNOTSUPP:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: device does not support dax");
> >> > + break;
> >> > + case -EINVAL:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: unaligned partition for dax");
> >> > + break;
> >> > + default:
> >> > + vfs_msg(sb, KERN_ERR,
> >> > + "error: dax access failed (%d)", err);
> >> > + }
> >> > + return err;
> >> > + }
> >> > +
> >> > + return 0;
> >> > +}
> >> > +EXPORT_SYMBOL_GPL(bdev_supports_dax);
> >>
> >> This patch should replace blkdev_dax_capable(), or just reuse that
> >> existing routine, or am I missing something?
> >
> > Good question. bdev_supports_dax() is a helper function tailored for the
> > filesystem's mount -o dax case. While blkdev_dax_capable() is similar, it
> > does not need error messages like "device does not support dax" since it
> > implicitly enables dax when capable. So, I think we can keep
> > blkdev_dax_capable(), but change it to call bdev_direct_access() so that
> > actual check is performed in a single place.
>
> Sounds good to me.
Can you name them consistently then? i.e. blkdev_dax_supported() and
blkdev_dax_capable()?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-05-09 21:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 0:29 [PATCH v3 0/5] Add alignment check for DAX mount Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` [PATCH v3 1/5] block: Add vfs_msg() interface Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-08 8:56 ` Christoph Hellwig
2016-05-06 0:29 ` [PATCH v3 2/5] block: Add bdev_supports_dax() for dax mount checks Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-08 8:57 ` Christoph Hellwig
2016-05-08 19:14 ` Dan Williams
2016-05-08 19:14 ` Dan Williams
2016-05-08 19:14 ` Dan Williams
2016-05-09 18:12 ` Toshi Kani
2016-05-09 18:12 ` Toshi Kani
2016-05-09 18:12 ` Toshi Kani
2016-05-09 18:23 ` Dan Williams
2016-05-09 18:23 ` Dan Williams
2016-05-09 18:23 ` Dan Williams
2016-05-09 21:19 ` Dave Chinner [this message]
2016-05-09 21:19 ` Dave Chinner
2016-05-09 21:19 ` Dave Chinner
2016-05-09 22:34 ` Toshi Kani
2016-05-09 22:34 ` Toshi Kani
2016-05-09 22:34 ` Toshi Kani
2016-05-09 22:50 ` Toshi Kani
2016-05-09 22:50 ` Toshi Kani
2016-05-09 22:50 ` Toshi Kani
2016-05-06 0:29 ` [PATCH v3 3/5] ext4: Add alignment check for DAX mount Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-09 8:15 ` Jan Kara
2016-05-09 8:15 ` Jan Kara
2016-05-09 8:15 ` Jan Kara
2016-05-06 0:29 ` [PATCH v3 4/5] ext2: " Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-08 8:59 ` Christoph Hellwig
2016-05-09 8:23 ` Jan Kara
2016-05-09 8:31 ` Jan Kara
2016-05-09 8:31 ` Jan Kara
2016-05-09 8:31 ` Jan Kara
2016-05-06 0:29 ` [PATCH v3 5/5] xfs: " Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-06 0:29 ` Toshi Kani
2016-05-08 8:58 ` Christoph Hellwig
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=20160509211903.GW18496@dastard \
--to=david@fromorbit.com \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=micah.parrish@hpe.com \
--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 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.