From: Boaz Harrosh <boaz@plexistor.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
Jens Axboe <axboe@fb.com>,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-nvdimm@lists.01.org, Toshi Kani <toshi.kani@hp.com>,
Dave Hansen <dave.hansen@intel.com>,
linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/9] pmem: Fixes and farther development (mm: add_persistent_memory)
Date: Tue, 09 Sep 2014 18:37:42 +0300 [thread overview]
Message-ID: <540F1EC6.4000504@plexistor.com> (raw)
In-Reply-To: <1409173922-7484-1-git-send-email-ross.zwisler@linux.intel.com>
On 08/28/2014 12:11 AM, Ross Zwisler wrote:
> PMEM is a modified version of the Block RAM Driver, BRD. The major difference
> is that BRD allocates its backing store pages from the page cache, whereas
> PMEM uses reserved memory that has been ioremapped.
>
> One benefit of this approach is that there is a direct mapping between
> filesystem block numbers and virtual addresses. In PMEM, filesystem blocks N,
> N+1, N+2, etc. will all be adjacent in the virtual memory space. This property
> allows us to set up PMD mappings (2 MiB) for DAX.
>
> This patch set is builds upon the work that Matthew Wilcox has been doing for
> DAX:
>
Let us not submit a driver with the wrong user visible API. Lets submit the
better API (and structure) I have sent.
> https://lkml.org/lkml/2014/8/27/31
>
> Specifically, my implementation of pmem_direct_access() in patch 4/4 uses API
> enhancements introduced in Matthew's DAX patch v10 02/21:
>
> https://lkml.org/lkml/2014/8/27/48
>
> Ross Zwisler (4):
> pmem: Initial version of persistent memory driver
> pmem: Add support for getgeo()
> pmem: Add support for rw_page()
> pmem: Add support for direct_access()
>
On top of the 4 above patches here is a list of changes:
[PATCH 1/9] SQUASHME: pmem: Remove unused #include headers
[PATCH 2/9] SQUASHME: pmem: Request from fdisk 4k alignment
[PATCH 3/9] SQUASHME: pmem: Let each device manage private memory region
[PATCH 4/9] SQUASHME: pmem: Support of multiple memory regions
These 4 need to be squashed into Ross's
[patch 1/4] pmem: Initial version of persistent memory driver
See below for a suggested new patch
[PATCH 5/9 v2] mm: Let sparse_{add,remove}_one_section receive a node_id
[PATCH 6/9 v2] mm: New add_persistent_memory/remove_persistent_memory
[PATCH 7/9 v2] pmem: Add support for page structs
Please need review by Toshi and mm people.
[PATCH 8/9] SQUASHME: pmem: Fixs to getgeo
[PATCH 9/9] pmem: KISS, remove register_blkdev
And some more development atop the initial version
All these patches can be viewed in this tree/branch:
git://git.open-osd.org/pmem.git branch pmem-jens-3.17-rc1
[http://git.open-osd.org/gitweb.cgi?p=pmem.git;a=shortlog;h=refs/heads/pmem-jens-3.17-rc1]
I have also prepared a new branch *pmem* which is already SQUASHED
And has my suggested changed commit logs for the combined patches
here is the commit-log:
aa85c80 Boaz Harrosh | pmem: KISS, remove register_blkdev
738203c Boaz Harrosh | pmem: Add support for page structs
9f50a54 Boaz Harrosh | mm: New add_persistent_memory/remove_persistent_memory
fdfab12 Yigal Korman | mm: Let sparse_{add,remove}_one_section receive a node_id
a477a87 Ross Zwisler | pmem: Add support for direct_access()
316a93a Ross Zwisler | pmem: Add support for rw_page()
6850353 Boaz Harrosh | SQUASHME: pmem: Fixs to getgeo
d78a84a Ross Zwisler | pmem: Add support for getgeo()
bb0eb45 Ross Zwisler | pmem: Initial version of persistent memory driver
All these patches can be viewed in this tree/branch:
git://git.open-osd.org/pmem.git branch pmem
[http://git.open-osd.org/gitweb.cgi?p=pmem.git;a=shortlog;h=refs/heads/pmem]
Specifically the first [bb0eb45] is needed so first version can be released with the
proper user visible API.
Ross please consider taking these patches (pmem branch) in your tree for submission?
Thanks
Boaz
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2014-09-09 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409173922-7484-1-git-send-email-ross.zwisler@linux.intel.com>
2014-09-09 15:37 ` Boaz Harrosh [this message]
2014-09-09 15:45 ` [PATCH 5/9] mm: Let sparse_{add,remove}_one_section receive a node_id Boaz Harrosh
2014-09-09 18:36 ` Dave Hansen
2014-09-10 10:07 ` Boaz Harrosh
2014-09-10 16:10 ` Dave Hansen
2014-09-10 17:25 ` Boaz Harrosh
2014-09-10 18:28 ` Dave Hansen
2014-09-11 8:39 ` Boaz Harrosh
2014-09-11 17:07 ` Dave Hansen
2014-09-14 9:36 ` Boaz Harrosh
2014-09-09 15:47 ` [PATCH 6/9] mm: New add_persistent_memory/remove_persistent_memory Boaz Harrosh
2014-09-09 15:48 ` [PATCH 7/9] pmem: Add support for page structs Boaz Harrosh
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=540F1EC6.4000504@plexistor.com \
--to=boaz@plexistor.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dave.hansen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ross.zwisler@linux.intel.com \
--cc=toshi.kani@hp.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;
as well as URLs for NNTP newsgroup(s).