On 11/04/2014 06:41 PM, Ross Zwisler wrote:
<>
>
> The UEFI organization is in the process of defining a generic specification
> for platform non-volatile memory resources. Essentially the thought was to
> wait until that was publicly available before adding any new device discovery
> capabilitie
oss
> > Zwisler; Jens Axboe; Nick Piggin; Kani, Toshimitsu; Knippers, Linda;
> > linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> > nvd...@lists.01.org; Matthew Wilcox
> > Subject: Re: [PATCH 1/4] pmem: Initial version of persistent memory
> > driver
.kernel.org; linux-kernel@vger.kernel.org; linux-
> nvd...@lists.01.org; Matthew Wilcox
> Subject: Re: [PATCH 1/4] pmem: Initial version of persistent memory
> driver
>
> On 11/03/2014 06:19 PM, Wilcox, Matthew R wrote:
...
>
> I wish you guys would actually review the corre
On 11/03/2014 06:19 PM, Wilcox, Matthew R wrote:
<>
>>> +config BLK_DEV_PMEM_COUNT
>>> + int "Default number of PMEM disks"
>>> + default "4"
>>
>> For real use I think a default of 1 would be better.
>
> For real use, you need at least two to run xfstests. This whole
> configuration mechani
I really wish people wouldn't use my Exchange email address for patches. It's
completely impossible to have a meaningful conversation this way. I've
resorted to inserting extra quotation marks by hand so people can stand at
least some chance of understanding what the hell's going on.
> > +con
"Elliott, Robert (Server Storage)" writes:
>> +config BLK_DEV_PMEM_COUNT
>> +int "Default number of PMEM disks"
>> +default "4"
>
> For real use I think a default of 1 would be better.
For "real" use, it will be the number of actual DIMMs, not a config
option, I would think. I don't tak
.org; linux-kernel@vger.kernel.org; linux-
> nvd...@lists.01.org
> Cc: Ross Zwisler
> Subject: [PATCH 1/4] pmem: Initial version of persistent memory
> driver
>
> PMEM is a new driver that presents a reserved range of memory as a
> block device. This is useful for developin
PMEM is a new driver that presents a reserved range of memory as a
block device. This is useful for developing with NV-DIMMs, and
can be used with volatile memory as a development platform.
Signed-off-by: Ross Zwisler
---
MAINTAINERS| 6 +
drivers/block/Kconfig | 41 ++
driv
8 matches
Mail list logo
