Question

The implementation tool should handle unloading the unused data in a fashion invisible to the user. Managing the data caching and memory hierarchy is left to tool implementation but it should be noted that failure to unload can affect the tool performance and capacity.

The user can optionally choose to call vpi_unload() to unload the data from (active) memory if the user application is done with accessing the data.

Calling vpi_unload() before releasing (freeing) traverse (collection) handles that are manipulating the data using vpi_free_object() is not recommended practice by users; the behavior of traversal using existing handles is not defined here. It is left up to tool implementation to decide how best to handle this. Tools shall, however, prevent creation of new traverse handles, after the call to vpi_unload(), by returning the appropriate fail codes in the respective creation routines.