2020
DOI: 10.1109/tcad.2019.2919035
|View full text |Cite
|
Sign up to set email alerts
|

Design of a Host Interface Logic for GC-Free SSDs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
3
3

Relationship

2
4

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 38 publications
0
6
0
Order By: Relevance
“…There are several reasons, but the greatest weakness of ISP ironically is that it needs to process data where data is stored, i.e., at the flash device. Flash cannot be directly used as block storage because of its low-level characteristics, such as I/O operation asymmetry and low reliability [10,37,38,55,56,78]. Thus, flash requires tight integration with multiple firmware and controller modules [98,99], which renders ISP difficult to be implemented within an SSD.…”
Section: Storage As a Gnn Acceleratormentioning
confidence: 99%
“…There are several reasons, but the greatest weakness of ISP ironically is that it needs to process data where data is stored, i.e., at the flash device. Flash cannot be directly used as block storage because of its low-level characteristics, such as I/O operation asymmetry and low reliability [10,37,38,55,56,78]. Thus, flash requires tight integration with multiple firmware and controller modules [98,99], which renders ISP difficult to be implemented within an SSD.…”
Section: Storage As a Gnn Acceleratormentioning
confidence: 99%
“…Garbage collection and resource contention on I/O buses (channels) of SSDs will block all incoming read/write requests to the same I/O buses, which must bring about greater turnaround time for these requests [10]. To be specific, the first two partial operations of GC (i.e., Read and Write) block the whole channel, and the last partial operation of Erase exclusively occupies the target chip [4,10].…”
Section: Related Workmentioning
confidence: 99%
“…Garbage collection and resource contention on I/O buses (channels) of SSDs will block all incoming read/write requests to the same I/O buses, which must bring about greater turnaround time for these requests [10]. To be specific, the first two partial operations of GC (i.e., Read and Write) block the whole channel, and the last partial operation of Erase exclusively occupies the target chip [4,10]. To minimize the negative effects on I/O latency caused by garbage collection, it is expected to either complete GC operations within less time [7,23,25] or place a higher priority to blocked I/O requests [1,14,26] or perform GC operations in the idle time intervals [4,9,11,16].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…This makes the power of internal DRAM buffers and controllers dominant for the I/O services rather than the power of backend flash. One of the performance bottlenecks that most SSDs suffer from is garbage collections [21,35,37,39,64]. Since flash does not allow to overwrite data without erasing a flash block, flash firmware [40,50,51] forwards all incoming overwrite requests to a new space (i.e., block), which was erased in a previous stage, and remaps the target addresses, associated with the request, to the new block.…”
Section: Is the Traditional Nvme Multi-queue Mechanism Also Affordabl...mentioning
confidence: 99%