aclmdlExecute

Applicability

Product

Supported

Atlas 350 Accelerator Card

Atlas A3 training product / Atlas A3 inference product

Atlas A2 training product / Atlas A2 inference product

Atlas 200I/500 A2 inference product

Atlas inference product

Atlas training product

Function Usage

Executes model inference until the result is returned.

The operations of loading, executing, and unloading a model must be performed in the same context. For details about how to create a context, see aclrtCreateContext.

Prototype

1
aclError aclmdlExecute(uint32_t modelId, const aclmdlDataset *input, aclmdlDataset *output)

Parameters

Parameter

Input/Output

Description

modelId

Input

Inference model ID.

After a model loading API (such as aclmdlLoadFromFile or aclmdlLoadFromMem.) is successfully called, the model ID is returned. This ID is used as the input of this API.

input

Input

Pointer to the input data for model inference. For details about the type definition, see aclmdlDataset.

output

Output

Pointer to the output data for model inference. For details about the type definition, see aclmdlDataset.

When calling aclCreateDataBuffer to create the aclDataBuffer type for storing output data of the corresponding index, you can pass nullptr to the data parameter and set size to 0 to create an empty aclDataBuffer type. During model execution, the system automatically calculates and allocates the index output memory. This method saves memory. However, you need to free the memory and reset the aclDataBuffer after using the data. In addition, memory copy is involved when the system allocates memory, which may cause performance loss.

The sample code for freeing the memory and resetting the aclDataBuffer is as follows:
1
2
3
4
aclDataBuffer *dataBuffer = aclmdlGetDatasetBuffer(output, 0); // Obtain the corresponding data buffer based on the index.
void *data = aclGetDataBufferAddr(dataBuffer);  // Obtain the device pointer to data.
aclrtFree(data ); // Free the device memory.
aclUpdateDataBuffer(dataBuffer, nullptr, 0); // Reset the content in the data buffer for next inference.

Returns

0 on success; else, failure. For details, see aclError.

Restrictions

  • If the same modelId is shared by multiple threads due to service requirements, locks must be added between user threads to ensure that operations of refreshing the input and output memories and executing inference are performed continuously. For example:
    // API call sequence of thread A:
    lock(handle1) -> aclrtMemcpy refreshes the input and output memory -> aclmdlExecute runs inference -> unlock(handle1)
    
    // API call sequence of thread B:
    lock(handle1) -> aclrtMemcpy refreshes the input and output memory -> aclmdlExecute runs inference -> unlock(handle1)
  • The memory for storing model input and output data is the device memory. You can call APIs such as aclrtMalloc and hi_mpi_dvpp_malloc to allocate device memory. The hi_mpi_dvpp_malloc API is a dedicated memory allocation API for media data processing. To reduce copy, the output of media data processing is used as the input of model inference to implement memory reuse. The address space accessed by media data processing is limited. To ensure sufficient memory during media data processing, you are advised to call other APIs (such as the aclrtMalloc API) to allocate memory for other functions (such as model loading) except media data processing.

Example

For details about the API call sequence and sample code, see Running a Model.