From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver Date: Tue, 16 Sep 2014 09:54:30 -0400 Message-ID: References: <1409173922-7484-1-git-send-email-ross.zwisler@linux.intel.com> <1409173922-7484-2-git-send-email-ross.zwisler@linux.intel.com> <540F2977.7010006@plexistor.com> <541050E5.60502@gmail.com> <54108ECA.6090200@plexistor.com> <54117D3A.3010305@plexistor.com> <5415797A.7000700@plexistor.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Dan Williams , Boaz Harrosh , Ross Zwisler , Jens Axboe , Matthew Wilcox , linux-fsdevel , "linux-kernel\@vger.kernel.org" , linux-nvdimm@ml01.01.org To: Boaz Harrosh Return-path: In-Reply-To: <5415797A.7000700@plexistor.com> (Boaz Harrosh's message of "Sun, 14 Sep 2014 14:18:18 +0300") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Boaz Harrosh writes: > On 09/11/2014 07:31 PM, Dan Williams wrote: > <> >> >> The point I am getting at is not requiring a priori knowledge of the >> physical memory map of a system. Rather, place holder variables to >> enable simple dynamic discovery. >> > > "simple dynamic discovery" does not yet exist and when the DDR4 NvDIMM > will be released then we still have those DDR3 out there which will > not work with the new discovery, which I need to support as well. Boaz, Are you telling me that vendors are shipping parts that present themselves as E820_RAM, and that you have to manually block off the addresses from the kernel using the kernel command line? If that is true, then that is just insane and unsupportable. All the hardware I have access to: 1) does not present itself as normal memory and 2) provides some means for discovering its address and size Cheers, Jeff