linux-kernel - Re: [GIT PULL] PMEM driver for v4.1

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150413093541.GA5147@lst.de>
Date:	Mon, 13 Apr 2015 11:35:41 +0200
From:	Christoph Hellwig <hch@....de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-nvdimm@...ts.01.org,
	Christoph Hellwig <hch@....de>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Boaz Harrosh <boaz@...xistor.com>
Subject: Re: [GIT PULL] PMEM driver for v4.1

On Mon, Apr 13, 2015 at 11:33:09AM +0200, Ingo Molnar wrote:
> Limitations: this is a regular block device, and since the pmem areas 
> are not struct page backed, they are invisible to the rest of the 
> system (other than the block IO device), so direct IO to/from pmem 
> areas, direct mmap() or XIP is not possible yet. The page cache will 
> also shadow and double buffer pmem contents, etc.

Unless you use the DAX support in ext2/4 and soon XFS, in which case
we avoid that double buffering when doing read/write and mmap
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/