Return-Path: Received: from gateway20.websitewelcome.com ([192.185.59.4]:34418 "EHLO gateway20.websitewelcome.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936362AbcIZBlo (ORCPT ); Sun, 25 Sep 2016 21:41:44 -0400 Received: from cm4.websitewelcome.com (unknown [108.167.139.16]) by gateway20.websitewelcome.com (Postfix) with ESMTP id 5B52A6EBF81A4 for ; Sun, 25 Sep 2016 20:18:42 -0500 (CDT) From: Stephen Bates To: linux-doc@vger.kernel.org, ross.zwisler@linux.intel.com, corbet@lwn.net, linux-fsdevel@vger.kernel.org Cc: Stephen Bates Subject: [PATCH] dax : Fix documentation with respect to struct pages Date: Sun, 25 Sep 2016 19:18:37 -0600 Message-Id: <1474852717-2161-1-git-send-email-sbates@raithlin.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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 --- 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