All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Stephen Bates <sbates@raithlin.com>
Cc: linux-doc@vger.kernel.org, ross.zwisler@linux.intel.com,
	corbet@lwn.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] dax : Fix documentation with respect to struct pages
Date: Tue, 27 Sep 2016 10:52:48 -0600	[thread overview]
Message-ID: <20160927165248.GB3377@linux.intel.com> (raw)
In-Reply-To: <1474852717-2161-1-git-send-email-sbates@raithlin.com>

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
> 

  reply	other threads:[~2016-09-27 16:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  1:18 [PATCH] dax : Fix documentation with respect to struct pages Stephen Bates
2016-09-27 16:52 ` Ross Zwisler [this message]
2016-10-01  6:52   ` Jonathan Corbet

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=20160927165248.GB3377@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sbates@raithlin.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.