You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Standards/scs-0100-v3-flavor-naming.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ description: |
14
14
15
15
## Introduction
16
16
17
-
This is the standard v3.2 for SCS Release 8.
17
+
This is the standard v3.3 for SCS Release 10.
18
18
Note that we intend to only extend it (so it's always backwards compatible),
19
19
but try to avoid changing in incompatible ways.
20
20
(See at the end for the v1 to v2 transition where we have not met that
@@ -192,7 +192,7 @@ latency (high IOPS) and bandwidth disk I/O. `n` storage is expected to survive
192
192
single-disk and single-node failure.
193
193
194
194
For specific requirements on the SSD and NVMe disks regarding IOPS and
195
-
power-loss protection, refer to Decision Record [scs-0110-ssd-flavors](https://github.com/SovereignCloudStack/standards/blob/main/Standards/scs-0110-v1-ssd-flavors.md).
195
+
power-loss protection, refer to Decision Record [scs-0110-ssd-flavors](https://docs.scs.community/standards/scs-0110-v1-ssd-flavors).
196
196
197
197
If the disk size is left out, the cloud is expected to allocate a disk (network or local)
198
198
that is large enough to fit the root file system (`min_disk` in image). This automatic
@@ -307,7 +307,8 @@ or Bare Metal Systems should indicate the Hypervisor according to the following
307
307
308
308
| hyp | Meaning |
309
309
| --- | ----------------- |
310
-
| kvm | KVM |
310
+
| kvm | KVM (w/ qemu) |
311
+
| chy | Cloud Hypervisor |
311
312
| xen | Xen |
312
313
| vmw | VMware |
313
314
| hyv | Hyper-V |
@@ -366,15 +367,15 @@ The options for arch are as follows:
366
367
The generation is vendor specific and can be left out, but it can only be specified in
367
368
conjunction with a vendor. At present, these values are possible:
368
369
369
-
| Generation | i (Intel x86-64) | z (AMD x86-64) |a (AArch64) | r (RISC-V) |
370
+
| Generation | i (Intel x86-64) | z (AMD x86-64) | a (AArch64)| r (RISC-V) |
It is recommended to leave out the `0` when specifying the old generation; this will
380
381
help the parser tool, which assumes 0 for an unspecified value and does leave it
@@ -386,7 +387,7 @@ out when generating the name for comparison. In other words: 0 has a meaning of
386
387
We don't differentiate between Zen-4 (Genoa) and Zen-4c (Bergamo); L3 cache per
387
388
Siena core is smaller on Bergamo and the frequency lower but the cores are otherwise
388
389
identical. As we already have a qualifier `h` that allows to specify higher frequencies
389
-
(which Genoa thus may use more and Bergamo not), we have enough distinction
390
+
(which Genoa thus may use and Bergamo not), we have enough distinction
390
391
capabilities. The same applies to Zen-5 (Turin) and Zen-5c (Turin Dense).
391
392
For intel with the server E-cores (Crestmont), these received their own
392
393
generation assignment, as the difference to the server P-cores (Redwood Cove)
@@ -437,9 +438,9 @@ Note that the vendor letter X is mandatory, generation and processing units are
437
438
|`A`| AMD | compute units (CUs) |
438
439
|`I`| Intel | execution units (EUs) |
439
440
440
-
For nVidia, the generation N can be f=Fermi, k=Kepler, m=Maxwell, p=Pascal, v=Volta, t=turing, a=Ampere, l=Ada Lovelace, g=Grace Hopper, ...,
441
-
for AMD GCN-x=0.x, RDNA1=1, C/RDNA2=2, C/RDNA3=3, C/RDNA3.5=3.5, C/RDNA4=4, ...
442
-
for Intel Gen9=0.9, Xe(12.1/DG1)=1, Xe(12.2)=2, Arc(12.7/DG2)=3 ...
441
+
For nVidia, the generation N can be f=Fermi, k=Kepler, m=Maxwell, p=Pascal, v=Volta, t=turing, a=Ampere, l=Ada Lovelace, g=Grace Hopper, b=Blackwell, ...,
442
+
for AMD GCN-x=0.x, CDNA-x=x, RDNA-x=x.1, RDNA-3.5=3.5, UDNA-x=x
443
+
for Intel Gen9=0.9, Xe(12.1/DG1)=1, Xe(12.2)=2, Arc(12.7/DG2)=3, BattleImage(20.0)=4, ...
443
444
(Note: This may need further work to properly reflect what's out there.)
444
445
445
446
The optional `h` suffix to the compute unit count indicates high-frequency GPU compute units.
0 commit comments