On Wed, Apr 01, 2015 at 06:18:54PM +0300, Boaz Harrosh wrote:
> You might as well rw & WRITE also for the above pmem_do_bvec call.
> If there can be such problem than the rw == READ inside
> pmem_do_bvec will fail as well.
Might be worth to pass a bool to pmem_do_bvec, but we're getting into
On Wed, Apr 01, 2015 at 06:18:54PM +0300, Boaz Harrosh wrote:
You might as well rw WRITE also for the above pmem_do_bvec call.
If there can be such problem than the rw == READ inside
pmem_do_bvec will fail as well.
Might be worth to pass a bool to pmem_do_bvec, but we're getting into
serious
On 04/01/2015 10:12 AM, Christoph Hellwig wrote:
> From: Ross Zwisler
>
> 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.
>
> This patch contains
From: Ross Zwisler
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.
This patch contains the initial driver from Ross Zwisler, with
various changes from
From: Ross Zwisler ross.zwis...@linux.intel.com
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.
This patch contains the initial driver from Ross Zwisler,
On 04/01/2015 10:12 AM, Christoph Hellwig wrote:
From: Ross Zwisler ross.zwis...@linux.intel.com
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.
6 matches
Mail list logo
