Function: dump_unreg_callback

Applicable Products

Product	Supported (√/x)
Ascend 950PR/Ascend 950DT	√
Atlas A3 training products/Atlas A3 inference products	√
Atlas A2 training products/Atlas A2 inference products	√
Atlas training products	√
Atlas inference products	√
Atlas 200I/500 A2 inference products	√

Description

Deregisters the dump data callback function.

The Function: init_dump, Function: dump_reg_callback, Function: dump_unreg_callback, and Function: finalize_dump APIs are used together to obtain the dump data by using the callback function. (The callback function registered by using this API needs to be implemented by the user. The implementation logic of the callback function includes obtaining the dump data and data length.) The specific scenarios are exemplified as follows:

Execute a model and obtain dump data through callback.
Function: init --> Function: dump_reg_callback --> Function: init_dump --> Model loading --> Model execution --> Function: finalize_dump --> Function: dump_unreg_callback --> Model unloading --> Function: finalize
Execute two different models and obtain dump data through callback. In this context, as long as the callback function is not deregistered by calling Function: dump_unreg_callback, you can obtain the dump data of both models through the callback function.
Function: init -- > Function: dump_reg_callback -- > Function: init_dump --> Model 1 loading --> Model 1 execution -->--> Model 2 loading --> Model 2 execution -- > Function: finalize_dump --> Model unloading -- > Function: dump_unreg_callback -- > Function: finalize

Prototype

C Prototype
1
void acldumpUnregCallback()
Python Function
1
acl.mdl.dump_unreg_callback()

Parameters

None

Return Values

None

Restrictions

acl.mdl.dump_unreg_callback must work with acl.mdl.dump_reg_callback and is valid only after acl.mdl.dump_reg_callback is called.

Parent topic: Dump Configuration