Star264
122
代码
代码
Issues3
Pull Requests6
Actions
项目讨论
Wiki
分析
Star264
122
cann-robotcann-robotsync 20260626
999c25d7创建于 6月27日历史提交
文件最后提交记录最后更新时间
Ascend_910B_DCMI_API
sync 20260626 Co-authored-by: ZLau22<liuaibin1@h-partners.com> # message auto-generated for no-merge-commit merge: !99 merge master into master sync 20260626 Created-by: ZLau22 Commit-by: ZLau22 Merged-by: cann-robot Description: ## 描述 <!--在这里详细描述你的改动，包括改动的原因和所采取的方法。--> ## 关联的Issue <!-- 如果这个PR是为了解决特定的Issue，请在这里提供Issue链接。例如：关联Issue #123--> <!-- 如果这个PR是为了解决特定的问题单，请在这里描述问题单单号。--> ## 测试 <!--描述进行了哪些测试来验证你的改动。包括但不限于二级冒烟、算子泛化等。--> ## 文档更新 <!--如果这个PR包含文档的更新，请在这里指出。例如：更新了README.md文件。--> ## 类型标签 <!-- [x] 表示选中 --> - [ ] Bug修复 - [ ] 新特性 - [ ] 性能优化 - [ ] 文档更新 - [ ] 其他，请描述： See merge request: cann/driver!99
1 个月前
README.md
sync 20260626 Co-authored-by: ZLau22<liuaibin1@h-partners.com> # message auto-generated for no-merge-commit merge: !99 merge master into master sync 20260626 Created-by: ZLau22 Commit-by: ZLau22 Merged-by: cann-robot Description: ## 描述 <!--在这里详细描述你的改动，包括改动的原因和所采取的方法。--> ## 关联的Issue <!-- 如果这个PR是为了解决特定的Issue，请在这里提供Issue链接。例如：关联Issue #123--> <!-- 如果这个PR是为了解决特定的问题单，请在这里描述问题单单号。--> ## 测试 <!--描述进行了哪些测试来验证你的改动。包括但不限于二级冒烟、算子泛化等。--> ## 文档更新 <!--如果这个PR包含文档的更新，请在这里指出。例如：更新了README.md文件。--> ## 类型标签 <!-- [x] 表示选中 --> - [ ] Bug修复 - [ ] 新特性 - [ ] 性能优化 - [ ] 文档更新 - [ ] 其他，请描述： See merge request: cann/driver!99
1 个月前
README

Interface List

interface_description

Overview

  • This document describes the DCMIs (DaVinci Card Management Interfaces). You can use these APIs to perform operations such as device management, configuration management, and chip reset.
  • DCMI is an NPU device management API. Once the driver is installed, it enables you to query NPU information and usage for status monitoring, and to perform operations including firmware upgrade, device information clearance, parameter configuration, and resource reset. You can call DCMI for secondary integration with third-party systems, based on business requirements.

Document Applicability

  • This document applies to Atlas 800T A2 training server, Atlas 200T A2 Box16 heterogeneous subrack, Atlas 300T A2 training card, A300I A2 inference card, Atlas 900 A2 PoD cluster basic unit, A200I A2 Box heterogeneous component, and Atlas 800I A2 inference server.
  • Only Ascend HDK 23.0.RC3 and later support the Atlas 900 A2 PoDc cluster basic unit. The Atlas 900 A2 PoDc cluster basic unit and Atlas 900 A2 PoD cluster basic unit use the same Ascend HDK software. Therefore, this document uses the Atlas 900 A2 PoD cluster basic unit as an example.

API Deployment Scenario Description

  • If a specific deployment scenario is not mentioned in the command or API description within this document, it indicates that the product does not support that scenario, and no such support is currently planned.
  • In the Support in different deployment scenarios tables in this document, Y means "supported", N means "not supported", and NA means "not applicable", indicating that the scenario is not planned.

Table 1 Deployment Scenario Definitions and Descriptions

Deployment Scenario

Sub-scenario

Description

Physical machine (PM)a

PM (bare metal)

NPUs run directly on PMs (bare metal).

PMa

PM + unprivileged container

Passthrough the physical server's NPU device into an unprivileged container for use.

PMa

PM + privileged container

Passthrough the physical server's NPU device into a privileged container for use.

Virtual machine (VM)b

VM passthrough

Dedicate an entire physical NPU for exclusive use by a single VM. Supported passthrough modes include: full-system (all NPUs), partial (a subset of NPUs), and single-device (one NPU)

VMb

VM passthrough + unprivileged container

Allocate an entire physical NPU to a VM and then pass its resources through to an unprivileged container running inside that VM.

VMb

VM passthrough + privileged container

Allocate an entire physical NPU to a VM and then pass its resources through to a privileged container running inside that VM.

Ascend virtual instance (AVI)c

PM + container-based AVI

On a PM, the npu-smi tool or DCMI is used to partition the NPU hardware resources into vNPUs based on user-defined requirements. The created vNPUs are then mounted to containers for use.

AVIc

PM + VM-based AVI

On a PM, the npu-smi tool or DCMI is used to partition the NPU hardware resources into vNPUs based on user-defined requirements. The created vNPUs are then allocated to the VM for use. A single vNPU can be allocated to only one VM, but a single VM can be mounted with multiple vNPUs.

AVIc

VM + container-based AVI

Partition the NPU hardware resources into vNPUs using the npu-smi tool or DCMI, based on user-defined requirements. Then allocate specified vNPUs to a VM, and mount the vNPUs to containers in the VM for use.

AVIc

VM passthrough + container-based AVI

Allocate a single physical NPU entirely to a VM. Then, within that VM, the NPU is partitioned into vNPUs using the npu-smi tool or DCMI based on user-defined requirements. Finally, these vNPUs are passed through to containers for use.

a: Operating NPU resources in a PM environment, including two scenarios: PM and PM + containers

b: Operating NPU resources in a VM environment, including two scenarios: VM passthrough and VM passthrough + containers

c: Use resource virtualization technology to partition one NPU into several vNPUs for mounting to VMs or containers, allowing one NPU to handle multiple computing tasks simultaneously. AVI implements this through computing power allocation, enabling secure, multi-tenant resource pooling and on-demand management, which greatly reduces costs and complexity.

API Usage Precautions

  • DCMIs cannot be concurrently used by multiple threads.
  • You are advised to compile DCMI-related executable files in a matching execution environment. Otherwise, glibc versions may be incompatible.
  • DSMIs have been deprecated since version 1.0.10 and was no longer be provided since 2023. Use corresponding DCMIs instead.
  • Unless otherwise specified, containers in this document refer to unprivileged containers.

Chip Reset API Description