From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "axboe@fb.com" <axboe@fb.com>, "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"agk@redhat.com" <agk@redhat.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"ross.zwisler@linux.intel.com" <ross.zwisler@linux.intel.com>,
"yigal@plexistor.com" <yigal@plexistor.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: dm stripe: add DAX support
Date: Wed, 13 Jul 2016 15:03:31 +0000 [thread overview]
Message-ID: <1468422189.8908.53.camel@hpe.com> (raw)
In-Reply-To: <20160713020100.GA5872@redhat.com>
On Tue, 2016-07-12 at 22:01 -0400, Mike Snitzer wrote:
> On Tue, Jul 12 2016 at 6:22pm -0400,
> Kani, Toshimitsu <toshi.kani@hpe.com> wrote:
> > On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> > >
:
> Thanks for putting this summary together. Unfortunately none of the DM
> changes can be queued for 4.8 until Jens takes the 2 block core patches:
> https://patchwork.kernel.org/patch/9196021/
> https://patchwork.kernel.org/patch/9196019/
>
> Not sure what the hold up and/or issue is with them. But I've asked
> twice (and implicilty a 3rd time here). Hopefully they land in time for
> 4.8.
Hi Jens,
Can you take the two patches above? These patches add QUEUE_FLAG_DAX and its
sysfs show func. They allow device-mapper to set dax-capability based on its
configuration, and also allow user applications to check dax-capability via
sysfs.
Thanks,
-Toshi
next prev parent reply other threads:[~2016-07-13 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 18:23 [PATCH] dm stripe: add DAX support Toshi Kani
2016-06-24 18:29 ` Mike Snitzer
2016-06-24 18:42 ` Kani, Toshimitsu
2016-07-12 22:22 ` Kani, Toshimitsu
2016-07-13 2:01 ` Mike Snitzer
2016-07-13 15:03 ` Kani, Toshimitsu [this message]
2016-07-21 0:01 ` Mike Snitzer
2016-07-21 3:03 ` Jens Axboe
2016-06-24 19:58 ` [PATCH] " kbuild test robot
2016-06-24 20:02 ` Mike Snitzer
2016-06-24 20:46 ` Kani, Toshimitsu
2016-06-24 19:59 ` [PATCH] " kbuild test robot
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=1468422189.8908.53.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=agk@redhat.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=snitzer@redhat.com \
--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).