diff options
author | Christoph Hellwig <hch@lst.de> | 2023-12-17 17:53:57 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2023-12-19 20:17:43 -0700 |
commit | 7437bb73f087e5f216f9c6603f5149d354e315af (patch) | |
tree | d3fbe5cb3e4e91e1062e9c25f7fd8a39ed761309 /fs/isofs | |
parent | a971ed8002110f211899279cd7295756d263b771 (diff) | |
download | linux-stable-7437bb73f087e5f216f9c6603f5149d354e315af.tar.gz linux-stable-7437bb73f087e5f216f9c6603f5149d354e315af.tar.bz2 linux-stable-7437bb73f087e5f216f9c6603f5149d354e315af.zip |
block: remove support for the host aware zone model
When zones were first added the SCSI and ATA specs, two different
models were supported (in addition to the drive managed one that
is invisible to the host):
- host managed where non-conventional zones there is strict requirement
to write at the write pointer, or else an error is returned
- host aware where a write point is maintained if writes always happen
at it, otherwise it is left in an under-defined state and the
sequential write preferred zones behave like conventional zones
(probably very badly performing ones, though)
Not surprisingly this lukewarm model didn't prove to be very useful and
was finally removed from the ZBC and SBC specs (NVMe never implemented
it). Due to to the easily disappearing write pointer host software
could never rely on the write pointer to actually be useful for say
recovery.
Fortunately only a few HDD prototypes shipped using this model which
never made it to mass production. Drop the support before it is too
late. Note that any such host aware prototype HDD can still be used
with Linux as we'll now treat it as a conventional HDD.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Link: https://lore.kernel.org/r/20231217165359.604246-4-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/isofs')
0 files changed, 0 insertions, 0 deletions