Custom Communication Operator - Point-to-Point Communication【免费下载链接】hccl集合通信库Huawei Collective Communication Library简称HCCL是基于昇腾AI处理器的高性能集合通信库为计算集群提供高性能、高可靠的通信方案项目地址: https://gitcode.com/cann/hcclSample DescriptionThis sample demonstrates how to develop Send and Recv point-to-point communication operators based on the HCCL communication programming interface. It covers the following features:Implement point-to-point communication operators based on the AICPU communication engine.Support independent building and deployment of custom operator packages.Directory Structure├── CMakeLists.txt # Compilation and build configuration file ├── op_host/ | ├── send.cc # HcclSendCustom operator implementation source file | ├── recv.cc # HcclRecvCustom operator implementation source file | ├── load_kernel.cc # AICPU Kernel loading logic on the Host side | ├── launch_kernel.cc # AICPU Kernel submission logic on the Host side | └── utils.cc # Utility module ├── op_kernel_aicpu/ | ├── libp2p_aicpu_kernel.json # AICPU Kernel operator description file | ├── aicpu_kernel.cc # AICPU Kernel implementation logic | └── exec_op.cc # AICPU operator orchestration logic ├── inc/ | ├── hccl_custom_p2p.h # Custom Send and Recv operator interface header file | ├── common.h # Common type header file | └── log.h # Log macro definitions ├── scripts/ | └── hccl_custom_p2p_check_cfg.xml # Signature configuration file └── testcase/ ├── main.cc # Sample implementation source file └── Makefile # Compilation and build configuration fileThe custom operator compilation project depends on the cmake configuration and the build.sh compilation script in the HCCL repository.cmake contains CMake configuration, MakeSelf packaging configuration, and so on.build.sh is the compilation entry for the project.1. Environment Preparation1.1 Environment RequirementsThis sample supports the following products in a single-server N-card configuration (N 2, even number):Atlas A3 Training Series Products / Atlas A3 Inference Series ProductsAtlas A2 Training Series ProductsThe following software dependencies are required for compiling this sample. Ensure that the version requirements are met:gcc and g: 7.3.0 to 13.3.xcmake 3.16.01.2 Install the CANN Toolkit Development Kit PackageRefer to the Ascend Documentation Center - CANN Software Installation Guide to install the latest version of the CANN Toolkit development kit package.1.3 Configure Environment VariablesRun the appropriate command to apply the environment variables.# Default path installation, using the root user as an example (for non-root users, replace /usr/local with ${HOME}) source /usr/local/Ascend/cann/set_env.sh # Specified path installation. ${install_path} indicates the actual CANN-Toolkit package installation path. # source ${install_path}/cann/set_env.sh2. Compiling the Custom Operator PackageThe HCCL repository provides a custom operator compilation and packaging project. This project depends on the following files in the repository:├── build.sh # Compilation entry in the hccl repository root directory ├── CMakeLists.txt # Compilation and build configuration file in the hccl repository root directory ├── cmake/ | ├── config.cmake # CMake variable definitions | ├── func.cmake # CMake function definitions | ├── package.cmake # Signature and packaging function definitions | └── makeself_custom.cmake # MakeSelf packaging logic ├── scripts/ ├── custom/install.sh # Custom operator package installation script └── sign/add_header_sign.py # AICPU operator package signing scriptTherefore, developers first need to download the hccl repository, then runbuild.shfrom the repository root directory for compilation, specifying the custom operator project path usingcustom_ops_path:# Download the hccl repository git clone https://gitcode.com/cann/hccl.git # Compile the custom operator package cd hccl bash build.sh --vendorcust --opsp2p --custom_ops_path./examples/04_custom_ops_p2pWhere:--vendorspecifies the custom operator identifier.--opsspecifies the custom operator name.--custom_ops_pathspecifies the custom operator project path.3. Installing the Custom Operator PackageThe custom operator installation package is located in the./build_outdirectory. Install it using the--installparameter:./build_out/cann-hccl_custom_p2p_linux-arch.run --install --install-pathascend_cann_pathWhere:archis the system architecture of the current compilation environment.ascend_cann_pathis an optional parameter indicating the CANN software package installation directory. The default value is the CANN software package path where theASCEND_CUSTOM_OPP_PATHorASCEND_OPP_PATHenvironment variable is located.The custom operator package installation information is as follows:Header file:${ASCEND_HOME_PATH}/opp/vendors/cust/include/hccl_custom_p2p.hDynamic library:${ASCEND_HOME_PATH}/opp/vendors/cust/lib64/libhccl_custom_p2p.soAICPU operator description file:${ASCEND_HOME_PATH}/opp/vendors/cust/aicpu/config/libp2p_aicpu_kernel.jsonAICPU operator package:${ASCEND_HOME_PATH}/opp/vendors/cust/aicpu/kernel/aicpu_hccl_custom_p2p.tar.gzInstallation script:${ASCEND_HOME_PATH}/opp/vendors/cust/scripts/install.sh${ASCEND_HOME_PATH}is the CANN-Toolkit installation path.4. Running the Custom Operator4.1 Disable AICPU Operator Signature VerificationThe AICPU operator packageaicpu_hccl_custom_p2p.tar.gzgenerated from source compilation is loaded to the Device when the service starts. During loading, the driver performs security signature verification by default to ensure that the package is trustworthy. Because the operator package compiled by developers from source does not contain signature information, disable the driver security signature verification mechanism.Method to disable signature verification:Use Ascend HDK 25.5.T2.B001 or later, and use the npu-smi tool provided with the Ascend HDK to disable signature verification. The following reference commands must be executed as the root user on the physical machine (using device 0 as an example).npu-smi set -t custom-op-secverify-enable -i 0 -d 1 # Enable signature verification configuration npu-smi set -t custom-op-secverify-mode -i 0 -d 0 # Disable user custom signature verificationWhere:-ispecifies the device ID, which is the NPU ID obtained from thenpu-smi info -lcommand.-dspecifies the attribute value for the corresponding configuration item.Note: Disabling the driver security signature verification mechanism carries certain security risks. Users must ensure the security and reliability of custom communication operators to prevent malicious attacks.4.2 Modify the AICPU WhitelistBy default, AICPU only loads packages configured in the whitelist. User-developed AICPU operator packages must be added to the whitelist:# Edit the configuration file, using the root user default installation path as an example vim /usr/local/Ascend/cann/conf/ascend_package_load.iniAppend the following content toascend_package_load.ini:name:aicpu_hccl_custom_p2p.tar.gz install_path:2 optional:true package_path:opp/vendors/cust/aicpu/kernel load_as_per_soc:falseField descriptions:name: tar package file name.install_path: Installation path enumeration value on the Device side. The AICPU kernel file path must be set to 2.optional: The default value is true. If the corresponding package does not exist, skip loading.package_path: Relative path of the tar package under the CANN Toolkit package on the Host side.load_as_per_soc: Whether to load for each chip type.4.3 Compile the SampleRun the following commands in theexamples/04_custom_ops_p2p/testcasedirectory:# Compile the sample make4.4 Run the SampleRun the following commands in theexamples/04_custom_ops_p2p/testcasedirectory:# Run the sample make test # Or run the sample binary directly export LD_LIBRARY_PATH${ASCEND_HOME_PATH}/opp/vendors/cust/lib64:${LD_LIBRARY_PATH} ./send_recv4.5 Sample OutputThesendBufcontent on even-numbered nodes is initialized to the Device ID of that node. The data is then sent to the next odd-numbered node. Therefore, each odd-numbered node receives the Device ID of the previous node.Found 8 NPU device(s) available rankId: 1, output: [ 0 0 0 0 0 0 0 0 ] rankId: 3, output: [ 2 2 2 2 2 2 2 2 ] rankId: 5, output: [ 4 4 4 4 4 4 4 4 ] rankId: 7, output: [ 6 6 6 6 6 6 6 6 ]【免费下载链接】hccl集合通信库Huawei Collective Communication Library简称HCCL是基于昇腾AI处理器的高性能集合通信库为计算集群提供高性能、高可靠的通信方案项目地址: https://gitcode.com/cann/hccl创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
Custom Communication Operator - Point-to-Point Communication【免费下载链接】hccl集合通信库Huawei Collective Communication Library简称HCCL是基于昇腾AI处理器的高性能集合通信库为计算集群提供高性能、高可靠的通信方案项目地址: https://gitcode.com/cann/hcclSample DescriptionThis sample demonstrates how to develop Send and Recv point-to-point communication operators based on the HCCL communication programming interface. It covers the following features:Implement point-to-point communication operators based on the AICPU communication engine.Support independent building and deployment of custom operator packages.Directory Structure├── CMakeLists.txt # Compilation and build configuration file ├── op_host/ | ├── send.cc # HcclSendCustom operator implementation source file | ├── recv.cc # HcclRecvCustom operator implementation source file | ├── load_kernel.cc # AICPU Kernel loading logic on the Host side | ├── launch_kernel.cc # AICPU Kernel submission logic on the Host side | └── utils.cc # Utility module ├── op_kernel_aicpu/ | ├── libp2p_aicpu_kernel.json # AICPU Kernel operator description file | ├── aicpu_kernel.cc # AICPU Kernel implementation logic | └── exec_op.cc # AICPU operator orchestration logic ├── inc/ | ├── hccl_custom_p2p.h # Custom Send and Recv operator interface header file | ├── common.h # Common type header file | └── log.h # Log macro definitions ├── scripts/ | └── hccl_custom_p2p_check_cfg.xml # Signature configuration file └── testcase/ ├── main.cc # Sample implementation source file └── Makefile # Compilation and build configuration fileThe custom operator compilation project depends on the cmake configuration and the build.sh compilation script in the HCCL repository.cmake contains CMake configuration, MakeSelf packaging configuration, and so on.build.sh is the compilation entry for the project.1. Environment Preparation1.1 Environment RequirementsThis sample supports the following products in a single-server N-card configuration (N 2, even number):Atlas A3 Training Series Products / Atlas A3 Inference Series ProductsAtlas A2 Training Series ProductsThe following software dependencies are required for compiling this sample. Ensure that the version requirements are met:gcc and g: 7.3.0 to 13.3.xcmake 3.16.01.2 Install the CANN Toolkit Development Kit PackageRefer to the Ascend Documentation Center - CANN Software Installation Guide to install the latest version of the CANN Toolkit development kit package.1.3 Configure Environment VariablesRun the appropriate command to apply the environment variables.# Default path installation, using the root user as an example (for non-root users, replace /usr/local with ${HOME}) source /usr/local/Ascend/cann/set_env.sh # Specified path installation. ${install_path} indicates the actual CANN-Toolkit package installation path. # source ${install_path}/cann/set_env.sh2. Compiling the Custom Operator PackageThe HCCL repository provides a custom operator compilation and packaging project. This project depends on the following files in the repository:├── build.sh # Compilation entry in the hccl repository root directory ├── CMakeLists.txt # Compilation and build configuration file in the hccl repository root directory ├── cmake/ | ├── config.cmake # CMake variable definitions | ├── func.cmake # CMake function definitions | ├── package.cmake # Signature and packaging function definitions | └── makeself_custom.cmake # MakeSelf packaging logic ├── scripts/ ├── custom/install.sh # Custom operator package installation script └── sign/add_header_sign.py # AICPU operator package signing scriptTherefore, developers first need to download the hccl repository, then runbuild.shfrom the repository root directory for compilation, specifying the custom operator project path usingcustom_ops_path:# Download the hccl repository git clone https://gitcode.com/cann/hccl.git # Compile the custom operator package cd hccl bash build.sh --vendorcust --opsp2p --custom_ops_path./examples/04_custom_ops_p2pWhere:--vendorspecifies the custom operator identifier.--opsspecifies the custom operator name.--custom_ops_pathspecifies the custom operator project path.3. Installing the Custom Operator PackageThe custom operator installation package is located in the./build_outdirectory. Install it using the--installparameter:./build_out/cann-hccl_custom_p2p_linux-arch.run --install --install-pathascend_cann_pathWhere:archis the system architecture of the current compilation environment.ascend_cann_pathis an optional parameter indicating the CANN software package installation directory. The default value is the CANN software package path where theASCEND_CUSTOM_OPP_PATHorASCEND_OPP_PATHenvironment variable is located.The custom operator package installation information is as follows:Header file:${ASCEND_HOME_PATH}/opp/vendors/cust/include/hccl_custom_p2p.hDynamic library:${ASCEND_HOME_PATH}/opp/vendors/cust/lib64/libhccl_custom_p2p.soAICPU operator description file:${ASCEND_HOME_PATH}/opp/vendors/cust/aicpu/config/libp2p_aicpu_kernel.jsonAICPU operator package:${ASCEND_HOME_PATH}/opp/vendors/cust/aicpu/kernel/aicpu_hccl_custom_p2p.tar.gzInstallation script:${ASCEND_HOME_PATH}/opp/vendors/cust/scripts/install.sh${ASCEND_HOME_PATH}is the CANN-Toolkit installation path.4. Running the Custom Operator4.1 Disable AICPU Operator Signature VerificationThe AICPU operator packageaicpu_hccl_custom_p2p.tar.gzgenerated from source compilation is loaded to the Device when the service starts. During loading, the driver performs security signature verification by default to ensure that the package is trustworthy. Because the operator package compiled by developers from source does not contain signature information, disable the driver security signature verification mechanism.Method to disable signature verification:Use Ascend HDK 25.5.T2.B001 or later, and use the npu-smi tool provided with the Ascend HDK to disable signature verification. The following reference commands must be executed as the root user on the physical machine (using device 0 as an example).npu-smi set -t custom-op-secverify-enable -i 0 -d 1 # Enable signature verification configuration npu-smi set -t custom-op-secverify-mode -i 0 -d 0 # Disable user custom signature verificationWhere:-ispecifies the device ID, which is the NPU ID obtained from thenpu-smi info -lcommand.-dspecifies the attribute value for the corresponding configuration item.Note: Disabling the driver security signature verification mechanism carries certain security risks. Users must ensure the security and reliability of custom communication operators to prevent malicious attacks.4.2 Modify the AICPU WhitelistBy default, AICPU only loads packages configured in the whitelist. User-developed AICPU operator packages must be added to the whitelist:# Edit the configuration file, using the root user default installation path as an example vim /usr/local/Ascend/cann/conf/ascend_package_load.iniAppend the following content toascend_package_load.ini:name:aicpu_hccl_custom_p2p.tar.gz install_path:2 optional:true package_path:opp/vendors/cust/aicpu/kernel load_as_per_soc:falseField descriptions:name: tar package file name.install_path: Installation path enumeration value on the Device side. The AICPU kernel file path must be set to 2.optional: The default value is true. If the corresponding package does not exist, skip loading.package_path: Relative path of the tar package under the CANN Toolkit package on the Host side.load_as_per_soc: Whether to load for each chip type.4.3 Compile the SampleRun the following commands in theexamples/04_custom_ops_p2p/testcasedirectory:# Compile the sample make4.4 Run the SampleRun the following commands in theexamples/04_custom_ops_p2p/testcasedirectory:# Run the sample make test # Or run the sample binary directly export LD_LIBRARY_PATH${ASCEND_HOME_PATH}/opp/vendors/cust/lib64:${LD_LIBRARY_PATH} ./send_recv4.5 Sample OutputThesendBufcontent on even-numbered nodes is initialized to the Device ID of that node. The data is then sent to the next odd-numbered node. Therefore, each odd-numbered node receives the Device ID of the previous node.Found 8 NPU device(s) available rankId: 1, output: [ 0 0 0 0 0 0 0 0 ] rankId: 3, output: [ 2 2 2 2 2 2 2 2 ] rankId: 5, output: [ 4 4 4 4 4 4 4 4 ] rankId: 7, output: [ 6 6 6 6 6 6 6 6 ]【免费下载链接】hccl集合通信库Huawei Collective Communication Library简称HCCL是基于昇腾AI处理器的高性能集合通信库为计算集群提供高性能、高可靠的通信方案项目地址: https://gitcode.com/cann/hccl创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
![[C++]内存管理：串顺序存储的内存回收](http://pic.xiahunao.cn/yaotu/[C++]内存管理：串顺序存储的内存回收)
