5 ms·
This is sort of the opposite of the RAM-based battery backed drives [1]. I can see this being immediately useful for things like large database servers: instead
by IgorPartola 12y ago
This is sort of the opposite of the RAM-based battery backed drives [1]. I can see this being immediately useful for things like large database servers: instead of re-priming caches on reboots you just have them already warmed up. You can also suddenly have a whole lot more "RAM" at the cost of its speed.
I do have a hard time picturing what this will look like if it was as fast as traditional RAM. If I can store everything in RAM, from the OS binaries, to the running processes, it certainly has a kind of elegance to it. Lots of microcontrollers already act this way: all your hardware has an address in a single address space, be at a hardware port, ROM, RAM, NVRAM, etc. However, I wonder how the modern UNIX OS will work with a system like this without block devices at all. I wonder if what it'd do is actually just use RAM disks, and years from now we'll still be doing this the way we do double emulation of the TTY. That'd be kind of sad since it means we can never get away from the concept of old block devices.
On the other hand it's damn convenient to be able to just append to a file and not have to worry about reallocating it. This means that perhaps all we'd need is a filesystem that's designed to work over RAM rather than over block devices.
[1] http://en.wikipedia.org/wiki/I-RAM http://en.wikipedia.org/wiki/I-RAM
- itchyouch 12y agoWhile block devices can go away, the notion of a file will probably continue to remain. We run clusters of ephemeral linux hosts, and while we use disk, we also have plenty of hosts that run diskless. The disk mount point just becomes a tmpfs mount and the required minimal installation is made on a tmpfs partition which amounts to a trivial amount for hosting busybox and some conf files in /etc. Linux does appear to understand that tmpfs backed filestores are already in memory and do not need to synchronize pages and flush out dirty pages. That whole caching/memory layer for this fake block device is just not used at all.
- IgorPartola 12y agoThat's right, we already have a filesystem backed by RAM: tmpfs. Except now it's no longer so tmp. I suppose then yes we don't have to do much in the way of emulating block devices: just run tmpfs or it's later revisions and know that everything is permanent. In that case, this is not much of a leap for the current OS's to support it, which is great. I wonder if this means that theoretically mmap() can become a one liner now.
- bkeroack 12y agoWhy bother? I see two possibilities: - Two separate address spaces, one volatile (RAM) and one persistent (SSD). "Writing" to persistent storage is as simple as "mov [src],[dst]". - One global address space, with a page attribute of "volatile" (true/false). Writing is just as simple as above. At that point the OS and userspace are free to create whatever abstractions are necessary on top. They don't necessarily need to be filesystems or files per se.
- 13 12y agoI do wish the iRam had stuck around longer. The 4GB limit makes it practically useless today, but a modern version of the same would be incredibly useful for some workloads.
- rsync 12y agoAren't there plenty of other PCIe ram-cards ? Like http://ddrdrive.com/ http://ddrdrive.com/ ? I didn't think there was any shortage of these kind of devices - especially given their common use in ZFS workloads as a SLOG.
- 13 12y agoI couldn't find any when I looked recently, even the one you've linked to is quite old (2009) and has the same 4GB (presumably 32bit) limit. If they were more common and in more realistic sizes I'd love to get my hands on one.
- rsync 12y ago"However, I wonder how the modern UNIX OS will work with a system like this without block devices at all." I don't think that's how it works - I think you get a special driver that presents the fast-storage-in-dimm-slot as a block device. So you still have a block device, it's just faster. Right ?
- eslaught 12y agoThe file system (and associated baggage) exist because of a fundamental disparity between the speed (and nearness to compute) of smaller memories and the convenience (but relative slowness) of larger ones. While SSDs do certainly close this gap, I find it difficult to imagine that this gap will ever entirely close; if anything, physics guarantees that compute units with small, nearby memories will always be far, far faster than more distant memories. You might argue that SSDs are "fast enough" to dispense with the inconvenience that imposes, but I can certainly find things I'd rather do with the performance.
- kalleboo 12y ago> If I can store everything in RAM, from the OS binaries, to the running processes, it certainly has a kind of elegance to it. Didn't Palm OS originally work this way? The early devices were too cheap for flash memory for anything more than the base OS, so they just stored everything in battery-backed RAM. If your batteries ran out, your device was wiped and had to be re-synced. Apps were run in-place in RAM. Then they had to hack in a bunch of workarounds when they added flash memory storage.