linux-kernel - Re: NVM Mapping API

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: <20120516215849.GC32221@kvack.org>
Date:	Wed, 16 May 2012 17:58:49 -0400
From:	Benjamin LaHaise <bcrl@...ck.org>
To:	Vyacheslav Dubeyko <slava@...eyko.com>
Cc:	Matthew Wilcox <willy@...ux.intel.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: NVM Mapping API

On Wed, May 16, 2012 at 10:24:13AM +0400, Vyacheslav Dubeyko wrote:
> Could you please share vision of these NVM technologies in more details?
> What capacity in bytes of of one NVM unit do we can expect? What about
> bad blocks and any other reliability issues of such NVM technologies?
> 
> I think that some more deep understanding of this can give possibility
> to imagine more deeply possible niche of such NVM units in future memory
> subsystem architecture.

Try having a look at the various articles on ReRAM, PRAM, FeRAM, MRAM...  
There are a number of technologies being actively developed.  For some 
quick info, Samsung has presented data on an 8Gbit 20nm device (see 
http://www.eetimes.com/electronics-news/4230958/ISSCC--Samsung-preps-8-Gbit-phase-change-memory ).  
It's hard to predict who will be first to market with a real production 
volume product, though.

The big question I have is what the actual interface for these types of 
memory will be.  If they're like actual RAM and can be mmap()ed into user 
space, it will be preferable to avoid as much of the overhead of the existing 
block infrastructure that most current day filesystems are built on top of.  
If the devices have only modest endurance limits, we may need to stick the 
kernel in the middle to prevent malicious code from wearing out a user's 
memory cells.

		-ben

--
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/