From WikiChip
Difference between revisions of "arm holdings/neoverse"
(neoverse) |
(→Cores) |
||
(14 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{armh title|Neoverse}} | {{armh title|Neoverse}} | ||
− | '''Neoverse''' is a | + | The '''Neoverse''' platform is a brand used by [[arm holdings|Arm]] to describe the {{arm|server|infrastructure side}} of their business. In other words, the Neoverse incorporates the technologies of the Arm ecosystem that spans from the [[edge]] to the [[cloud]]. |
+ | == Overview == | ||
+ | [[File:arm techcon 2018 neoverse announcement.jpg|thumb|right|Drew Henry Neoverse announcement at Arm TechCon 2018.]] | ||
+ | [[arm holdings|Arm]] introduced the 'Neoverse' at Arm TechCon 2018. It's a general term that may be used by both Arm and their partners who work on the Arm ecosystem as it pertains to infrastructure (e.g., routers, switching, servers). The term covers everything from the [[edge]] to the [[cloud]] and is not part of the client ecosystem which is covered by the {{\\|Cortex}} brand. | ||
− | {{ | + | == Cores == |
+ | [[File:arm_server_roadmap_techcon_2018.jpg|thumb|right|Neoverse Roadmap.]] | ||
+ | As part of the [[Neoverse]], [[Arm]] is releasing specific [[microarchitectures]] with higher performance | ||
+ | :and power targets for the server markets. | ||
+ | |||
+ | |||
+ | {| class="wikitable" style="text-align: center; | ||
+ | |- | ||
+ | | colspan="4" | Older platforms | ||
+ | |- | ||
+ | | [[2015]] || colspan="3" | {{armh|Cosmos|l=arch}} ([[Cortex]]) | ||
+ | |- | ||
+ | ! !! High-throughput !! High-performance !! HPC | ||
+ | |- | ||
+ | | [[2019]] || {{armh|Neoverse E1|l=arch}} (''{{armh|Helios|l=arch}}'') <hr>(Cortex-A65AE) || {{armh|Neoverse N1|l=arch}} (''{{armh|Ares|l=arch}}'') <hr>(Cortex-A76AE) || | ||
+ | |- | ||
+ | | [[2020]] || || || | ||
+ | |- | ||
+ | | [[2021]] || {{armh|Neoverse E2|l=arch}} <hr>(Cortex-A510) || {{armh|Neoverse N2|l=arch}} (''{{armh|Perseus|l=arch}}'') <hr>Neoverse CSS N2 (''Genesis'') || {{armh|Neoverse V1|l=arch}} (''{{armh|Zeus|l=arch}}'') | ||
+ | |- | ||
+ | | [[2022]] || || || {{armh|Neoverse V2|l=arch}} (''{{armh|Demeter|l=arch}}'') | ||
+ | |- | ||
+ | | [[2023]] || {{armh|Neoverse E3|l=arch}} (''{{armh|Aphrodite|l=arch}}'') || {{armh|Neoverse N3|l=arch}} (''{{armh|Hermes|l=arch}}'') <hr>Neoverse CSS N3 (''Pioneer'') || {{armh|Neoverse V3|l=arch}} (''{{armh|Poseidon|l=arch}}'') <hr>Neoverse CSS V3 (''Voyager'') | ||
+ | |- | ||
+ | | [[2024]] || || || Neoverse V3AE (''Poseidon-AE'') <br>Neoverse VN (''Poseidon-VN'') | ||
+ | |- | ||
+ | | [[2025]] || {{armh|Neoverse E4|l=arch}} (''{{armh|Lycius|l=arch}}'') || {{armh|Neoverse N4|l=arch}} (''{{armh|Dionysus|l=arch}}'') <hr>Neoverse CSS N4 (''Ranger'') || {{armh|Neoverse V4|l=arch}} (''{{armh|Adonis|l=arch}}'') <hr>Neoverse CSS V4 (''Vega'') | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | * '''Gen 1:''' Neoverse E1 (''Helios''), Neoverse N1 (''Ares''), Neoverse V1 (''Zeus'') | ||
+ | * '''Gen 2:''' Neoverse E2, Neoverse N2 (''Perseus''), Neoverse V2 (''Demeter'') | ||
+ | : Neoverse CSS N2 (''Genesis'') • [https://www.nextplatform.com/2024/02/21/arm-neoverse-roadmap-brings-cpu-designs-but-no-big-fat-gpu/ Neoverse Roadmap] • [https://www.nextplatform.com/wp-content/uploads/2024/02/arm-neoverse-roadmap-2024-1.jpg Tables 2024] | ||
+ | * '''Gen 3:''' Neoverse E3 (''Aphrodite''), Neoverse N3 (''Hermes''), Neoverse V3 (''Poseidon'') | ||
+ | : Neoverse V3AE (''Poseidon-AE''), Neoverse VN (''Poseidon-VN'') [Auto] | ||
+ | : Neoverse CSS N3 (''Pioneer''), Neoverse CSS V3 (''Voyager'') <!-- | ||
+ | : “Pioneer” for CSS N3 and “Voyager” for CSS V3; Old Testament: “Exodus” and “Leviticus” ? --> | ||
+ | * '''Gen 4:''' Neoverse E4 (''Lycius''), Neoverse N4 (''Dionysus''), Neoverse V4 (''Adonis'') | ||
+ | : Neoverse CSS N4 (''Ranger''), Neoverse CSS V4 (''Vega'') | ||
+ | |||
+ | == See also == | ||
+ | * {{arm|Servers|ARM Servers}} | ||
+ | * {{armh|Cortex}} | ||
+ | |||
+ | [[category:arm holdings]] |
Latest revision as of 03:00, 14 March 2025
The Neoverse platform is a brand used by Arm to describe the infrastructure side of their business. In other words, the Neoverse incorporates the technologies of the Arm ecosystem that spans from the edge to the cloud.
Overview[edit]
Arm introduced the 'Neoverse' at Arm TechCon 2018. It's a general term that may be used by both Arm and their partners who work on the Arm ecosystem as it pertains to infrastructure (e.g., routers, switching, servers). The term covers everything from the edge to the cloud and is not part of the client ecosystem which is covered by the Cortex brand.
Cores[edit]
As part of the Neoverse, Arm is releasing specific microarchitectures with higher performance
- and power targets for the server markets.
Older platforms | |||
2015 | Cosmos (Cortex) | ||
High-throughput | High-performance | HPC | |
---|---|---|---|
2019 | Neoverse E1 (Helios) (Cortex-A65AE) |
Neoverse N1 (Ares) (Cortex-A76AE) |
|
2020 | |||
2021 | Neoverse E2 (Cortex-A510) |
Neoverse N2 (Perseus) Neoverse CSS N2 (Genesis) |
Neoverse V1 (Zeus) |
2022 | Neoverse V2 (Demeter) | ||
2023 | Neoverse E3 (Aphrodite) | Neoverse N3 (Hermes) Neoverse CSS N3 (Pioneer) |
Neoverse V3 (Poseidon) Neoverse CSS V3 (Voyager) |
2024 | Neoverse V3AE (Poseidon-AE) Neoverse VN (Poseidon-VN) | ||
2025 | Neoverse E4 (Lycius) | Neoverse N4 (Dionysus) Neoverse CSS N4 (Ranger) |
Neoverse V4 (Adonis) Neoverse CSS V4 (Vega) |
- Gen 1: Neoverse E1 (Helios), Neoverse N1 (Ares), Neoverse V1 (Zeus)
- Gen 2: Neoverse E2, Neoverse N2 (Perseus), Neoverse V2 (Demeter)
- Neoverse CSS N2 (Genesis) • Neoverse Roadmap • Tables 2024
- Gen 3: Neoverse E3 (Aphrodite), Neoverse N3 (Hermes), Neoverse V3 (Poseidon)
- Neoverse V3AE (Poseidon-AE), Neoverse VN (Poseidon-VN) [Auto]
- Neoverse CSS N3 (Pioneer), Neoverse CSS V3 (Voyager)
- Gen 4: Neoverse E4 (Lycius), Neoverse N4 (Dionysus), Neoverse V4 (Adonis)
- Neoverse CSS N4 (Ranger), Neoverse CSS V4 (Vega)