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: <20120516173523.GK22985@linux.intel.com>
Date:	Wed, 16 May 2012 13:35:23 -0400
From:	Matthew Wilcox <willy@...ux.intel.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: NVM Mapping API

On Wed, May 16, 2012 at 10:52:00AM +0100, James Bottomley wrote:
> On Tue, 2012-05-15 at 09:34 -0400, Matthew Wilcox wrote:
> > There are a number of interesting non-volatile memory (NVM) technologies
> > being developed.  Some of them promise DRAM-comparable latencies and
> > bandwidths.  At Intel, we've been thinking about various ways to present
> > those to software.  This is a first draft of an API that supports the
> > operations we see as necessary.  Patches can follow easily enough once
> > we've settled on an API.
> 
> If we start from first principles, does this mean it's usable as DRAM?
> Meaning do we even need a non-memory API for it?  The only difference
> would be that some pieces of our RAM become non-volatile.

I'm not talking about a specific piece of technology, I'm assuming that
one of the competing storage technologies will eventually make it to
widespread production usage.  Let's assume what we have is DRAM with a
giant battery on it.

So, while we can use it just as DRAM, we're not taking advantage of the
persistent aspect of it if we don't have an API that lets us find the
data we wrote before the last reboot.  And that sounds like a filesystem
to me.

> Or is there some impediment (like durability, or degradation on rewrite)
> which makes this unsuitable as a complete DRAM replacement?

The idea behind using a different filesystem for different NVM types is
that we can hide those kinds of impediments in the filesystem.  By the
way, did you know DRAM degrades on every write?  I think it's on the
order of 10^20 writes (and CPU caches hide many writes to heavily-used
cache lines), so it's a long way away from MLC or even SLC rates, but
it does exist.

> Alternatively, if it's not really DRAM, I think the UNIX file
> abstraction makes sense (it's a piece of memory presented as something
> like a filehandle with open, close, seek, read, write and mmap), but
> it's less clear that it should be an actual file system.  The reason is
> that to present a VFS interface, you have to already have fixed the
> format of the actual filesystem on the memory because we can't nest
> filesystems (well, not without doing artificial loopbacks).  Again, this
> might make sense if there's some architectural reason why the flash
> region has to have a specific layout, but your post doesn't shed any
> light on this.

We can certainly present a block interface to allow using unmodified
standard filesystems on top of chunks of this NVM.  That's probably not
the optimum way for a filesystem to use it though; there's really no
point in constructing a bio to carry data down to a layer that's simply
going to do a memcpy().
--
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/