Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1404288
| From | Xiong Zhou <xzhou@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory |
| Date | 2016-05-20 11:50 +0200 |
| Message-ID | <rAPe9-3PB-11@gated-at.bofh.it> (permalink) |
| References | <rAgJs-6ZU-7@gated-at.bofh.it> <rAgJs-6ZU-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, May 18, 2016 at 01:56:16PM -0700, Dan Williams wrote: > Device DAX is the device-centric analogue of Filesystem DAX > (CONFIG_FS_DAX). It allows memory ranges to be allocated and mapped > without need of an intervening file system. Device DAX is strict, > precise and predictable. Specifically this interface: > > 1/ Guarantees fault granularity with respect to a given page size (pte, > pmd, or pud) set at configuration time. > > 2/ Enforces deterministic behavior by being strict about what fault > scenarios are supported. > > For example, by forcing MADV_DONTFORK semantics and omitting MAP_PRIVATE > support device-dax guarantees that a mapping always behaves/performs the > same once established. It is the "what you see is what you get" access > mechanism to differentiated memory vs filesystem DAX which has > filesystem specific implementation semantics. > > Persistent memory is the first target, but the mechanism is also > targeted for exclusive allocations of performance differentiated memory > ranges. > > This commit is limited to the base device driver infrastructure to > associate a dax device with pmem range. > > Cc: Jeff Moyer <jmoyer@redhat.com> > Cc: Christoph Hellwig <hch@lst.de> > Cc: Andrew Morton <akpm@linux-foundation.org> > Cc: Dave Hansen <dave.hansen@linux.intel.com> > Cc: Ross Zwisler <ross.zwisler@linux.intel.com> > Signed-off-by: Dan Williams <dan.j.williams@intel.com> > --- > drivers/Kconfig | 2 > drivers/Makefile | 1 > drivers/dax/Kconfig | 25 +++ > drivers/dax/Makefile | 4 + > drivers/dax/dax.c | 253 +++++++++++++++++++++++++++++++++++ > drivers/dax/dax.h | 24 +++ > drivers/dax/pmem.c | 158 ++++++++++++++++++++++ An entry in MAINTAINERS for these new files ? Thanks, Xiong
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v3 0/5] "Device DAX" for persistent memory Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
[PATCH v3 3/5] /dev/dax, core: file operations and dax-mmap Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
Re: [PATCH v3 3/5] /dev/dax, core: file operations and dax-mmap Johannes Thumshirn <jthumshirn@suse.de> - 2016-05-20 10:00 +0200
[PATCH v3 5/5] libnvdimm: release ida resources Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
Re: [PATCH v3 5/5] libnvdimm: release ida resources Johannes Thumshirn <jthumshirn@suse.de> - 2016-05-20 09:40 +0200
[PATCH v3 4/5] Revert "block: enable dax for raw block devices" Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
[PATCH v3 1/5] libnvdimm: stop requiring a driver ->remove() method Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
Re: [PATCH v3 1/5] libnvdimm: stop requiring a driver ->remove() method Johannes Thumshirn <jthumshirn@suse.de> - 2016-05-20 09:40 +0200
[PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory Dan Williams <dan.j.williams@intel.com> - 2016-05-18 23:00 +0200
Re: [PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory Johannes Thumshirn <jthumshirn@suse.de> - 2016-05-20 10:10 +0200
Re: [PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory Xiong Zhou <xzhou@redhat.com> - 2016-05-20 11:50 +0200
csiph-web