public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hpe.com>
To: akpm@linux-foundation.org, dan.j.williams@intel.com
Cc: tytso@mit.edu, jack@suse.cz, linux-nvdimm@lists.01.org,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
	adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org, willy@linux.intel.com,
	ross.zwisler@linux.intel.com, linux-ext4@vger.kernel.org,
	kirill.shutemov@linux.intel.com
Subject: [PATCH v2 0/5] Align mmap address for DAX pmd mappings
Date: Tue, 12 Apr 2016 14:39:14 -0600	[thread overview]
Message-ID: <1460493555-31611-1-git-send-email-toshi.kani@hpe.com> (raw)

When CONFIG_FS_DAX_PMD is set, DAX supports mmap() using pmd page
size.  This feature relies on both mmap virtual address and FS
block (i.e. physical address) to be aligned by the pmd page size.
Users can use mkfs options to specify FS to align block allocations.
However, aligning mmap address requires code changes to existing
applications for providing a pmd-aligned address to mmap().

For instance, fio with "ioengine=mmap" performs I/Os with mmap() [1].
It calls mmap() with a NULL address, which needs to be changed to
provide a pmd-aligned address for testing with DAX pmd mappings.
Changing all applications that call mmap() with NULL is undesirable.

This patch-set extends filesystems to align an mmap address for
a DAX file so that unmodified applications can use DAX pmd mappings.

[1]: https://github.com/axboe/fio/blob/master/engines/mmap.c

v2:
 - Change filesystems to provide their get_unmapped_area().
   (Matthew Wilcox)
 - Add more description about the benefit. (Matthew Wilcox)

---
Toshi Kani (5):
 1/5 dax: add dax_get_unmapped_area for pmd mappings
 2/5 ext4: call dax_get_unmapped_area() for DAX pmd mappings
 3/5 xfs: call dax_get_unmapped_area() for DAX pmd mappings
 4/5 ext2: call dax_get_unmapped_area() for DAX pmd mappings
 5/5 block: call dax_get_unmapped_area() for DAX pmd mappings

---
 fs/block_dev.c      |  3 +++
 fs/dax.c            | 45 +++++++++++++++++++++++++++++++++++++++++++++
 fs/ext2/file.c      |  3 +++
 fs/ext4/file.c      |  3 +++
 fs/xfs/xfs_file.c   |  3 +++
 include/linux/dax.h |  2 ++
 6 files changed, 59 insertions(+)

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2016-04-12 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 20:39 Toshi Kani [this message]
2016-04-12 20:39 ` [PATCH v2 1/5] dax: add dax_get_unmapped_area for pmd mappings Toshi Kani
2016-04-13  3:18   ` Matthew Wilcox
2016-04-13 14:55     ` Toshi Kani

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=1460493555-31611-1-git-send-email-toshi.kani@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@linux.intel.com \
    --cc=xfs@oss.sgi.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