From: Mike Snitzer <snitzer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild test robot <lkp@intel.com>,
linux-nvdimm@lists.01.org, Michael Ellerman <mpe@ellerman.id.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Bart Van Assche <Bart.VanAssche@wdc.com>,
dm-devel@redhat.com, Paul Mackerras <paulus@samba.org>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH v3 0/2] dax, dm: stop requiring dax for device-mapper
Date: Wed, 2 Aug 2017 14:55:38 -0400 [thread overview]
Message-ID: <20170802185537.GA16551@redhat.com> (raw)
In-Reply-To: <150169667935.39569.15808116323143633486.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed, Aug 02 2017 at 1:57pm -0400,
Dan Williams <dan.j.williams@intel.com> wrote:
> Changes since v2 [1]:
> * rebase on -next to integrate with commit 273752c9ff03 "dm, dax: Make
> sure dm_dax_flush() is called if device supports it" (kbuild robot)
> * fix CONFIG_DAX dependencies to upgrade CONFIG_DAX=m to CONFIG_DAX=y
> (kbuild robot)
>
> [1]: https://www.spinics.net/lists/kernel/msg2570522.html
>
> ---
>
> Bart points out that the DAX core is unconditionally enabled if
> device-mapper is enabled. Add some config machinery and some
> stub-static-inline routines to allow dax infrastructure to be deleted
> from device-mapper at compile time.
>
> Since this depends on commit 273752c9ff03 that's already in -next, this
> should go through the device-mapper tree.
Commit 273752c9ff03eb83856601b2a3458218bb949e46 is upstream as of
v4.13-rc3 -- so no real need to have this go via linux-dm.git
That said, I don't mind picking it up once we are satisfied with the
implementation. I'll start reviewing shortly.
Mike
_______________________________________________
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: Mike Snitzer <snitzer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild test robot <lkp@intel.com>,
linux-nvdimm@lists.01.org, Michael Ellerman <mpe@ellerman.id.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
dm-devel@redhat.com, Paul Mackerras <paulus@samba.org>,
Alasdair Kergon <agk@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH v3 0/2] dax, dm: stop requiring dax for device-mapper
Date: Wed, 2 Aug 2017 14:55:38 -0400 [thread overview]
Message-ID: <20170802185537.GA16551@redhat.com> (raw)
In-Reply-To: <150169667935.39569.15808116323143633486.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed, Aug 02 2017 at 1:57pm -0400,
Dan Williams <dan.j.williams@intel.com> wrote:
> Changes since v2 [1]:
> * rebase on -next to integrate with commit 273752c9ff03 "dm, dax: Make
> sure dm_dax_flush() is called if device supports it" (kbuild robot)
> * fix CONFIG_DAX dependencies to upgrade CONFIG_DAX=m to CONFIG_DAX=y
> (kbuild robot)
>
> [1]: https://www.spinics.net/lists/kernel/msg2570522.html
>
> ---
>
> Bart points out that the DAX core is unconditionally enabled if
> device-mapper is enabled. Add some config machinery and some
> stub-static-inline routines to allow dax infrastructure to be deleted
> from device-mapper at compile time.
>
> Since this depends on commit 273752c9ff03 that's already in -next, this
> should go through the device-mapper tree.
Commit 273752c9ff03eb83856601b2a3458218bb949e46 is upstream as of
v4.13-rc3 -- so no real need to have this go via linux-dm.git
That said, I don't mind picking it up once we are satisfied with the
implementation. I'll start reviewing shortly.
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
Michael Ellerman <mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>,
Heiko Carstens
<heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>,
dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Paul Mackerras <paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
Gerald Schaefer
<gerald.schaefer-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Benjamin Herrenschmidt
<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
Martin Schwidefsky
<schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Alasdair Kergon <agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v3 0/2] dax, dm: stop requiring dax for device-mapper
Date: Wed, 2 Aug 2017 14:55:38 -0400 [thread overview]
Message-ID: <20170802185537.GA16551@redhat.com> (raw)
In-Reply-To: <150169667935.39569.15808116323143633486.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Wed, Aug 02 2017 at 1:57pm -0400,
Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> Changes since v2 [1]:
> * rebase on -next to integrate with commit 273752c9ff03 "dm, dax: Make
> sure dm_dax_flush() is called if device supports it" (kbuild robot)
> * fix CONFIG_DAX dependencies to upgrade CONFIG_DAX=m to CONFIG_DAX=y
> (kbuild robot)
>
> [1]: https://www.spinics.net/lists/kernel/msg2570522.html
>
> ---
>
> Bart points out that the DAX core is unconditionally enabled if
> device-mapper is enabled. Add some config machinery and some
> stub-static-inline routines to allow dax infrastructure to be deleted
> from device-mapper at compile time.
>
> Since this depends on commit 273752c9ff03 that's already in -next, this
> should go through the device-mapper tree.
Commit 273752c9ff03eb83856601b2a3458218bb949e46 is upstream as of
v4.13-rc3 -- so no real need to have this go via linux-dm.git
That said, I don't mind picking it up once we are satisfied with the
implementation. I'll start reviewing shortly.
Mike
next prev parent reply other threads:[~2017-08-02 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 17:57 [PATCH v3 0/2] dax, dm: stop requiring dax for device-mapper Dan Williams
2017-08-02 17:57 ` Dan Williams
2017-08-02 17:58 ` [PATCH v3 1/2] dax: introduce CONFIG_DAX_DRIVER Dan Williams
2017-08-02 17:58 ` Dan Williams
2017-08-02 17:58 ` Dan Williams
2017-08-02 17:58 ` [PATCH v3 2/2] dm: allow device-mapper to operate without dax support Dan Williams
2017-08-02 17:58 ` Dan Williams
2017-09-11 14:41 ` Mike Snitzer
2017-09-11 14:41 ` Mike Snitzer
2017-09-11 15:56 ` Dan Williams
2017-09-11 15:56 ` Dan Williams
2017-09-11 15:56 ` Dan Williams
2017-08-02 18:55 ` Mike Snitzer [this message]
2017-08-02 18:55 ` [PATCH v3 0/2] dax, dm: stop requiring dax for device-mapper Mike Snitzer
2017-08-02 18:55 ` Mike Snitzer
2017-09-09 18:56 ` Dan Williams
2017-09-09 18:56 ` 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=20170802185537.GA16551@redhat.com \
--to=snitzer@redhat.com \
--cc=Bart.VanAssche@wdc.com \
--cc=agk@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.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.