From: Boaz Harrosh <boaz@plexistor.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, riel@redhat.com, linux-nvdimm@lists.01.org,
hch@infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Linux-nvdimm] [PATCH 0/6] Add persistent memory driver
Date: Wed, 18 Mar 2015 13:08:54 +0200 [thread overview]
Message-ID: <55095CC6.4070404@plexistor.com> (raw)
In-Reply-To: <1426540380-24503-1-git-send-email-ross.zwisler@linux.intel.com>
On 03/16/2015 11:12 PM, 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, which has been merged into the v4.0 kernel series.
>
> For more information on PMEM and for some instructions on how to use it, please
> check out PMEM's github tree:
>
> https://github.com/01org/prd
>
> Cc: linux-nvdimm@lists.01.org
> Cc: linux-fsdevel@vger.kernel.org
> Cc: axboe@kernel.dk
> Cc: hch@infradead.org
> Cc: riel@redhat.com
>
> Boaz Harrosh (1):
> pmem: Let each device manage private memory region
>
Not signed-off-by me.
> Ross Zwisler (5):
> pmem: Initial version of persistent memory driver
This is the wrong code
> pmem: Add support for getgeo()
We do not need this patch
> pmem: Add support for rw_page()
> pmem: Add support for direct_access()
> pmem: Clean up includes
>
NACK!
This is the wrong pmem driver, the wrong API and the wrong bad copy/paste
from brd code.
(And thanks Ross for not CCing me I have lots of mail to read every day,
Seriously this is rude, what do I need to feel?)
And very Seriously. Ross what is that joke Kconfig and module-param
API, how it is relevant to anything and how it is getting us close
to what pmem really needs to be, with the auto-probe. Is this your
wait wait we done lots of new work on this? It did not change one
bit from the original brd copy/paste.
Boaz
> MAINTAINERS | 6 +
> drivers/block/Kconfig | 41 +++++
> drivers/block/Makefile | 1 +
> drivers/block/pmem.c | 401 +++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 449 insertions(+)
> create mode 100644 drivers/block/pmem.c
>
prev parent reply other threads:[~2015-03-18 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 21:12 [PATCH 0/6] Add persistent memory driver Ross Zwisler
2015-03-16 21:12 ` [PATCH 1/6] pmem: Initial version of " Ross Zwisler
2015-03-17 18:53 ` Paul Bolle
2015-03-16 21:12 ` [PATCH 2/6] pmem: Add support for getgeo() Ross Zwisler
2015-03-16 21:12 ` [PATCH 3/6] pmem: Add support for rw_page() Ross Zwisler
2015-03-16 21:12 ` [PATCH 4/6] pmem: Add support for direct_access() Ross Zwisler
2015-03-16 21:12 ` [PATCH 5/6] pmem: Clean up includes Ross Zwisler
2015-03-16 21:13 ` [PATCH 6/6] pmem: Let each device manage private memory region Ross Zwisler
2015-03-18 10:57 ` Boaz Harrosh
2015-03-18 11:08 ` Boaz Harrosh [this message]
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=55095CC6.4070404@plexistor.com \
--to=boaz@plexistor.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=riel@redhat.com \
--cc=ross.zwisler@linux.intel.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).