3 ms·
You'd need a filesystem that was pretty careful to write a very large chunk extremely sequeuntially. That's easiest with Host-aware SMR (to have some idea the
by loeg 7y ago
You'd need a filesystem that was pretty careful to write a very large chunk extremely sequeuntially. That's easiest with Host-aware SMR (to have some idea the size of the zones) or a linear LogFS.
- Dylan16807 7y agoYes, I agree entirely. But the point I'm making is that "host-aware" should be good enough for this type of use. Even though it's still drive-managed, the internal logic in the drive should pass through certain write patterns without interference. And you can make the host aware through feeding in a few parameters; it doesn't necessarily have to interrogate the drive. In other words, I'm disagreeing with the idea that this big laundry list of things would need to be updated. The filesystem should be sufficient if these drives act in a way that's at all reasonable.
- loeg 7y agoAh, maybe. It’s not a big step from aware to managed, though. The zoned api is actually quite simple: what are the zones?, open zone, finish zone. The filesystem that’s tolerant of these characteristics is the hard part.
- Dylan16807 7y agoIt's a big step in terms of product segmentation. You don't want to sell a drive that just fails to work in most machines.