lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Sep 2014 09:54:30 -0400
From:	Jeff Moyer <>
To:	Boaz Harrosh <>
Cc:	Dan Williams <>,
	Boaz Harrosh <>,
	Ross Zwisler <>,
	Jens Axboe <>,
	Matthew Wilcox <>,
	linux-fsdevel <>,
	"linux-kernel\" <>,
Subject: Re: [Linux-nvdimm] [PATCH v2] pmem: Initial version of persistent memory driver

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.


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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists