From: Mike Snitzer <snitzer@redhat.com>
To: "Kani, Toshimitsu" <toshi.kani@hpe.com>
Cc: "yigal@plexistor.com" <yigal@plexistor.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"schwidefsky@de.ibm.com" <schwidefsky@de.ibm.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"agk@redhat.com" <agk@redhat.com>
Subject: Re: [PATCH v2 1/3] block: add QUEUE_FLAG_DAX for devices to advertise their DAX support
Date: Thu, 23 Jun 2016 17:11:32 -0400 [thread overview]
Message-ID: <20160623211131.GA9163@redhat.com> (raw)
In-Reply-To: <1466702773.3504.363.camel@hpe.com>
On Thu, Jun 23 2016 at 1:36pm -0400,
Kani, Toshimitsu <toshi.kani@hpe.com> wrote:
> On Thu, 2016-06-23 at 19:31 +0300, Yigal Korman wrote:
> > On Thu, Jun 23, 2016 at 2:54 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > >
> > >
> > > Currently, presence of direct_access() in block_device_operations
> > > indicates support of DAX on its block device. Because
> > > block_device_operations is instantiated with 'const', this DAX
> > > capablity may not be enabled conditinally.
> > >
> > > In preparation for supporting DAX to device-mapper devices, add
> > > QUEUE_FLAG_DAX to request_queue flags to advertise their DAX
> > > support. This will allow to set the DAX capability based on how
> > > mapped device is composed.
> >
> > Hi Toshi,
> > This patch is very helpful!
> > I think QUEUE_FLAG_DAX can also help with identifying dax devices in
> > userspace.
> > Perhaps you'd be willing to squash the patch below with this one or
> > add it to your submission?
>
> Hi Yigal,
>
> Good idea. Mike can probably take it into his tree, but I will include it
> into the series if I needed to submit v3.
>
> Acked-by: Toshi Kani <toshi.kani@hpe.com>
As you can see I sent out v3 of this set. Jens will need to pick up the
"block:" patches but I'll pick up the DM patches once Jens does so.
next prev parent reply other threads:[~2016-06-23 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 23:54 [PATCH v2 0/3] Support DAX for device-mapper dm-linear devices Toshi Kani
2016-06-22 23:54 ` [PATCH v2 1/3] block: add QUEUE_FLAG_DAX for devices to advertise their DAX support Toshi Kani
2016-06-23 16:31 ` Yigal Korman
2016-06-23 17:36 ` Kani, Toshimitsu
2016-06-23 18:05 ` Yigal Korman
2016-06-23 18:10 ` Dan Williams
2016-06-23 21:11 ` Mike Snitzer [this message]
2016-06-22 23:54 ` [PATCH v2 2/3] dm: add infrastructure for " Toshi Kani
2016-06-22 23:54 ` [PATCH v2 3/3] dm linear: add " Toshi Kani
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=20160623211131.GA9163@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=toshi.kani@hpe.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yigal@plexistor.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 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).