5 ms·
Disks have had complex CPUs on them for awhile, might as well go full mainframe and admit they're smart storage subsystems and put them on the first class bus.
by h2odragon 5y ago
Disks have had complex CPUs on them for awhile, might as well go full mainframe and admit they're smart storage subsystems and put them on the first class bus. is "DASD" still an IBM trademark?
Of course theres a long history of "multiple interface" drives which are always ugly hacks that turn up as rare collectors items and examples of boondoggle.
- DaiPlusPlus 5y ago> and admit they're smart storage subsystems and put them on the first class bus. is "DASD" still an IBM trademark? Y'know that eventually we'll be running everything off Intel's Optane non-volatile RAM: we won't have block-addressable storage anymore, everything will be directly byte-addressable. All of the storage abstractions that have popped-up over the past decades (tracks, heads, cylinders, ew, block-addressing, unnecessarily large block sizes, etc) will be obsolete because we'll already have perfect-storage. It's not quite DASD, but it's much better.
- trasz 5y agoOptane didn’t exactly take the market by storm. Also: flash memory doesn’t work this way; its inherently organized into blocks/pages.
- DaiPlusPlus 5y agoThe "Optane" that Intel released as their 3DXPoint NVMe brand, (and quietly withdrew it recently) isn't the same Optane as their byte-addressable non-volatile storage+RAM combo. It isn't Flash memory with blocks/pages, it really is byte-addressable: https://dl.acm.org/doi/10.1145/3357526.3357568 https://dl.acm.org/doi/10.1145/3357526.3357568 "true" Optane hasn't taken over the scene because, to my knowledge, there's no commercially supported OS that's built around a unified memory model (heck, why not have a single memory-space?) for both storage and memory. We can't even write software that can just reanimate itself from a process image that would be automagically persisted in the unified storage model. We've got a long way to go before we'll see operating systems and applications that take advantage of it.
- spijdar 5y agoBut RAM is itself accessed in blocks. The process is hidden to software, but memory is always fetched in word-aligned blocks. It doesn't contradict your point, but just pointing out that even DRAM is pulled in chunks not unlike traditional drives (if you squint) (Of course, getting those chunks down to cache line sizes does open up a lot of possibilities...)
- trasz 5y agoWell, yeah, the cacheline can be considered a kind of a 64-byte block. But it doesn't work like this because of how RAM works - you could access DRAM in words if you wished to; it's just that it doesn't make sense because of CPU cache. For flash, the blocks (and pages) are inherent to its design and there is no way around it. Also, RAM "block size" is 64B, while for flash its more like 4kB. CPU cache will "deblock" the 64B blocks, but it can't efficiently do it for 4kB ones. And then there's the speed. Does replacing PCIe with a memory bus actually make a performance difference that's measurable given flash latency?
- dragontamer 5y agoDRAM is accessed in rows of maybe 4096 bytes or so, the size of the sense amplifiers. Also known as a bank. The transfer itself is 64 bytes at a time (burst length 8 for DDR4 x 64 bit channel). But internally, the RAS (row address strobe) is the access of note.
- namibj 5y agoDDR4 DIMMs have (almost?) exclusively 8kiB pages. If you have 2 channels with interleaving, like AFAIK the default on all current x86 desktop platforms, you get the same 16kiB effective page size as the typical[0] TLB compressing (which smashes the 4 4kiB pagetable entries in a cacheline worth of lowest-level pagetable into a single virtual 16kiB TLB entry if they have the same attributes and look exactly as a smashed 16kiB page table entry would look like (alignment, contiguous, etc.)). [0]: Zen3 does it for sure, but I think I also saw it somewhere else.
- hakfoo 5y agoI feel like you're going to need different filesystem concepts to deal with full byte addressable storage. There's a lot of simplifications you can use knowing everything is a world of 512 byte/8k blocks. Everything that's a linked list of blocks would suddenly be lists of "start and offset" instead, because you might have a file was fragmented as "1Mb at offset A, 32 bytes at offset B, and 5Mb at offset C". You'd likely need some tradeoffs for minimum fragment sizes to avoid a file sharding into a million 32-byte fragments and requiring a huge number of distinct reads to load, and maximum sizes that would be manageable without overloading the recipient device's buffer.
- hinkley 5y agoStarting to see more complaints about subsystems that Linux is not really in control of becoming more and more numerous. Rumors seem to be that Oxide Computers is trying to make an OS to control many of these but I suspect the end result will be treating the case as a heterogeneous cluster. It's possible that these will continue acting cooperatively rather than anyone being under the misapprehension that they're actually 'in charge', but perhaps a different division of labor will give us some cool benefits. Would still love to see SQLite or Postgres running directly on a storage subsystem.
- jabl 5y agoSee also https://www.youtube.com/watch?v=36myc8wQhLo https://www.youtube.com/watch?v=36myc8wQhLo I'm not sure what Oxide is doing, but creating an OS to replace the firmware on all kinds of 3rd party devices sounds, well, quite quixotic. I'd guess it's more like a common OS for the firmware of their own hardware (rack controllers and whatnot).
- hinkley 5y ago> firmware on all kinds of 3rd party devices sounds, well, quite quixotic You could say the same about device drivers in Linux. It was a very long process that required many, many hands. It took a long time even to cover all of the common devices let alone the more obscure ones.
- ants_a 5y agoOr alternatively, toss in a network interface and have drives PXE boot an application specific firmware and spin up a ceph-osd or similar server.