linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] dax : Fix documentation with respect to struct pages
@ 2016-09-26  1:18 Stephen Bates
  2016-09-27 16:52 ` Ross Zwisler
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Bates @ 2016-09-26  1:18 UTC (permalink / raw)
  To: linux-doc, ross.zwisler, corbet, linux-fsdevel; +Cc: Stephen Bates

The documentation for dax is not up to date with respect to the struct
page support available in some of the device drivers that utilize
it.

Signed-off-by: Stephen Bates <sbates@raithlin.com>
---
 Documentation/filesystems/dax.txt | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/Documentation/filesystems/dax.txt b/Documentation/filesystems/dax.txt
index 0c16a22..23d18b8 100644
--- a/Documentation/filesystems/dax.txt
+++ b/Documentation/filesystems/dax.txt
@@ -123,9 +123,12 @@ The DAX code does not work correctly on architectures which have virtually
 mapped caches such as ARM, MIPS and SPARC.
 
 Calling get_user_pages() on a range of user memory that has been mmaped
-from a DAX file will fail as there are no 'struct page' to describe
-those pages.  This problem is being worked on.  That means that O_DIRECT
-reads/writes to those memory ranges from a non-DAX file will fail (note
-that O_DIRECT reads/writes _of a DAX file_ do work, it is the memory
-that is being accessed that is key here).  Other things that will not
-work include RDMA, sendfile() and splice().
+from a DAX file will fail when there are no 'struct page' to describe
+those pages.  This problem has been addressed in some device drivers
+by adding optional struct page support for pages under the control of
+the driver (see CONFIG_NVDIMM_PFN in drivers/nvdimm for an example of
+how to do this). In the non struct page cases O_DIRECT reads/writes to
+those memory ranges from a non-DAX file will fail (note that O_DIRECT
+reads/writes _of a DAX file_ do work, it is the memory that is being
+accessed that is key here).  Other things that will not work in the
+non struct page case include RDMA, sendfile() and splice().
-- 
2.5.0


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] dax : Fix documentation with respect to struct pages
  2016-09-26  1:18 [PATCH] dax : Fix documentation with respect to struct pages Stephen Bates
@ 2016-09-27 16:52 ` Ross Zwisler
  2016-10-01  6:52   ` Jonathan Corbet
  0 siblings, 1 reply; 3+ messages in thread
From: Ross Zwisler @ 2016-09-27 16:52 UTC (permalink / raw)
  To: Stephen Bates; +Cc: linux-doc, ross.zwisler, corbet, linux-fsdevel

On Sun, Sep 25, 2016 at 07:18:37PM -0600, Stephen Bates wrote:
> The documentation for dax is not up to date with respect to the struct
> page support available in some of the device drivers that utilize
> it.
> 
> Signed-off-by: Stephen Bates <sbates@raithlin.com>

Great, thanks for updating this.

Acked-by: Ross Zwisler <ross.zwisler@linux.intel.com>

> ---
>  Documentation/filesystems/dax.txt | 15 +++++++++------
>  1 file changed, 9 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/filesystems/dax.txt b/Documentation/filesystems/dax.txt
> index 0c16a22..23d18b8 100644
> --- a/Documentation/filesystems/dax.txt
> +++ b/Documentation/filesystems/dax.txt
> @@ -123,9 +123,12 @@ The DAX code does not work correctly on architectures which have virtually
>  mapped caches such as ARM, MIPS and SPARC.
>  
>  Calling get_user_pages() on a range of user memory that has been mmaped
> -from a DAX file will fail as there are no 'struct page' to describe
> -those pages.  This problem is being worked on.  That means that O_DIRECT
> -reads/writes to those memory ranges from a non-DAX file will fail (note
> -that O_DIRECT reads/writes _of a DAX file_ do work, it is the memory
> -that is being accessed that is key here).  Other things that will not
> -work include RDMA, sendfile() and splice().
> +from a DAX file will fail when there are no 'struct page' to describe
> +those pages.  This problem has been addressed in some device drivers
> +by adding optional struct page support for pages under the control of
> +the driver (see CONFIG_NVDIMM_PFN in drivers/nvdimm for an example of
> +how to do this). In the non struct page cases O_DIRECT reads/writes to
> +those memory ranges from a non-DAX file will fail (note that O_DIRECT
> +reads/writes _of a DAX file_ do work, it is the memory that is being
> +accessed that is key here).  Other things that will not work in the
> +non struct page case include RDMA, sendfile() and splice().
> -- 
> 2.5.0
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] dax : Fix documentation with respect to struct pages
  2016-09-27 16:52 ` Ross Zwisler
@ 2016-10-01  6:52   ` Jonathan Corbet
  0 siblings, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2016-10-01  6:52 UTC (permalink / raw)
  To: Ross Zwisler; +Cc: Stephen Bates, linux-doc, linux-fsdevel

On Tue, 27 Sep 2016 10:52:48 -0600
Ross Zwisler <ross.zwisler@linux.intel.com> wrote:

> On Sun, Sep 25, 2016 at 07:18:37PM -0600, Stephen Bates wrote:
> > The documentation for dax is not up to date with respect to the struct
> > page support available in some of the device drivers that utilize
> > it.
> > 
> > Signed-off-by: Stephen Bates <sbates@raithlin.com>  
> 
> Great, thanks for updating this.
> 
> Acked-by: Ross Zwisler <ross.zwisler@linux.intel.com>

Applied to the docs tree, thanks.

jon

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-10-01  6:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-26  1:18 [PATCH] dax : Fix documentation with respect to struct pages Stephen Bates
2016-09-27 16:52 ` Ross Zwisler
2016-10-01  6:52   ` Jonathan Corbet

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).