On Tue, Apr 28, 2015 at 5:56 AM, Christoph Hellwig wrote:
> On Sat, Apr 18, 2015 at 12:37:09PM -0700, Dan Williams wrote:
>> At this point in the patch series I agree, but in later patches we
>> take advantage of nd bus services. "[PATCH 15/21] nd: pmem label sets
>> and namespace instantiation"
On Sat, Apr 18, 2015 at 12:37:09PM -0700, Dan Williams wrote:
> At this point in the patch series I agree, but in later patches we
> take advantage of nd bus services. "[PATCH 15/21] nd: pmem label sets
> and namespace instantiation" adds support for labeled pmem namespaces,
> and in "[PATCH
On Sat, Apr 18, 2015 at 12:37:09PM -0700, Dan Williams wrote:
At this point in the patch series I agree, but in later patches we
take advantage of nd bus services. [PATCH 15/21] nd: pmem label sets
and namespace instantiation adds support for labeled pmem namespaces,
and in [PATCH 19/21] nd:
On Tue, Apr 28, 2015 at 5:56 AM, Christoph Hellwig h...@infradead.org wrote:
On Sat, Apr 18, 2015 at 12:37:09PM -0700, Dan Williams wrote:
At this point in the patch series I agree, but in later patches we
take advantage of nd bus services. [PATCH 15/21] nd: pmem label sets
and namespace
On Fri, Apr 17, 2015 at 11:38 PM, Christoph Hellwig wrote:
> On Fri, Apr 17, 2015 at 09:36:18PM -0400, Dan Williams wrote:
>> nd_pmem attaches to persistent memory regions and namespaces emitted by
>> the nd subsystem, and, same as the original pmem driver, presents the
>> system-physical-address
On Fri, Apr 17, 2015 at 09:36:18PM -0400, Dan Williams wrote:
> nd_pmem attaches to persistent memory regions and namespaces emitted by
> the nd subsystem, and, same as the original pmem driver, presents the
> system-physical-address range as a block device.
I don't think there is any need to
On Fri, Apr 17, 2015 at 11:38 PM, Christoph Hellwig h...@lst.de wrote:
On Fri, Apr 17, 2015 at 09:36:18PM -0400, Dan Williams wrote:
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
On Fri, Apr 17, 2015 at 09:36:18PM -0400, Dan Williams wrote:
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
I don't think there is any need to move
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
Cc: Andy Lutomirski
Cc: Boaz Harrosh
Cc: H. Peter Anvin
Cc: Jens Axboe
Cc: Ingo Molnar
Cc: Christoph
nd_pmem attaches to persistent memory regions and namespaces emitted by
the nd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
Cc: Andy Lutomirski l...@amacapital.net
Cc: Boaz Harrosh b...@plexistor.com
Cc: H. Peter Anvin
10 matches
Mail list logo
