2023
DOI: 10.48550/arxiv.2301.06672
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Custom 8-bit floating point value format for reducing shared memory bank conflict in approximate nearest neighbor search

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2023
2023
2023
2023

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 0 publications
0
1
0
Order By: Relevance
“…However, the machine could be synthesized using floating-point formats such as bfloat16, float16, and TensorFloat32 [44], by implementing the required logic in the PEs, and by adjusting, in general, memory size. It would be also possible to maintain memory capacity unvaried and store intermediate layer results using 8-bit floating point arithmetic, for instance e5m3 or e4m4 [45]. In particular, e5m3 can represent normalized float16 numbers with lower accuracy but enable a small overhead for float32 conversion.…”
Section: Single Perceptron Linear Vector Processor a High-level Archi...mentioning
confidence: 99%
“…However, the machine could be synthesized using floating-point formats such as bfloat16, float16, and TensorFloat32 [44], by implementing the required logic in the PEs, and by adjusting, in general, memory size. It would be also possible to maintain memory capacity unvaried and store intermediate layer results using 8-bit floating point arithmetic, for instance e5m3 or e4m4 [45]. In particular, e5m3 can represent normalized float16 numbers with lower accuracy but enable a small overhead for float32 conversion.…”
Section: Single Perceptron Linear Vector Processor a High-level Archi...mentioning
confidence: 99%