VLSI KoreaNVIDIA Ampere Architecture In-Depth
NVIDIA specifies 40 GB of HBM2 for the A100 discussed in the architecture article.
- Published
- 2020-05-14
- Retrieved
- 2026-09-08
Semiconductor graph
NVIDIA A100 Tensor Core GPU6 entities and 5 documented connections shown.
Drag the map or use pan buttons to move. Tab to a node or connection and press Enter to inspect its evidence. Arrows follow the actual claim direction.
CompanyChip / productTechnologyPlace / facility
Select a connection for its evidenceRelationships & evidence (5)
| Subject | Relationship | Object | Status | Evidence |
|---|---|---|---|---|
| NVIDIA A100 Tensor Core GPU | HBM2 | SUPPORTEDSource-reported snapshot: 2020-05-14 | Why are these connected?This is the cited 40 GB configuration; later A100 variants use HBM2e. | |
| NVIDIA A100 Tensor Core GPU | NVIDIA third-generation NVLink | SUPPORTEDSource-reported snapshot: 2020-05-14 | Why are these connected?Interconnect availability and topology can vary by A100 form factor/system. NVIDIA Ampere Architecture In-DepthNVIDIA says third-generation NVLink is implemented in A100 GPUs.
| |
| NVIDIA GA100 GPU | NVIDIA A100 Tensor Core GPU | SUPPORTEDSource-reported snapshot: 2020-05-14 | Why are these connected?GA100 die and A100 product identity. NVIDIA Ampere Architecture In-DepthNVIDIA states that GA100 powers the A100 GPU product.
| |
| NVIDIA A100 Tensor Core GPU | NVIDIA | SUPPORTEDSource-reported snapshot: 2020-05-14 | Why are these connected?Product authorship statement; not a fabrication or supply-chain claim. NVIDIA Ampere Architecture In-DepthNVIDIA presents A100 as its GPU product based on its Ampere GPU architecture.
| |
| NVIDIA A100 Tensor Core GPU | NVIDIA Ampere architecture | SUPPORTEDSource-reported snapshot: 2020-05-14 | Why are these connected?Applies to A100, not every Ampere product. NVIDIA Ampere Architecture In-DepthNVIDIA states that A100 is based on the Ampere GPU architecture.
|
Find an evidence path
Find a documented path
From NVIDIA A100 Tensor Core GPU · up to two relationship steps.
A path retains its original claims. Shared technology does not establish a supply contract.
6 nodes · 5 claims
Scope
Relationships may describe different dates. A path does not establish simultaneous activity. Bounded source-backed collection. Missing or filtered connections do not establish absence. Supported does not mean independently verified.