Extended Library Functions - Part 1
Extended Library Functions - Part 2
dat_registry_add_provider(3DAT)
dat_registry_list_providers(3DAT)
dat_registry_remove_provider(3DAT)
dat_set_consumer_context(3DAT)
devid_deviceid_to_nmlist(3DEVID)
di_link_next_by_lnode(3DEVINFO)
di_link_next_by_node(3DEVINFO)
di_lnode_private_get(3DEVINFO)
di_lnode_private_set(3DEVINFO)
di_minor_private_get(3DEVINFO)
di_minor_private_set(3DEVINFO)
di_prom_prop_lookup_bytes(3DEVINFO)
di_prom_prop_lookup_ints(3DEVINFO)
di_prom_prop_lookup_strings(3DEVINFO)
di_prop_lookup_bytes(3DEVINFO)
di_prop_lookup_int64(3DEVINFO)
di_prop_lookup_strings(3DEVINFO)
DmiListComponentsByClass(3DMI)
ea_match_object_catalog(3EXACCT)
Extended Library Functions - Part 3
Extended Library Functions - Part 4
- create an RMR for the specified Protection Zone
cc [ flag… ] file… -ldat [ library… ] #include <dat/udat.h> DAT_RETURN dat_rmr_create( IN DAT_PZ_HANDLE pz_handle, OUT DAT_RMR_HANDLE *rmr_handle )
Handle for an instance of the Protection Zone.
Handle for the created instance of an RMR.
The dat_rmr_create() function creates an RMR for the specified Protection Zone. This operation is relatively heavy. The created RMR can be bound to a memory region within the LMR through a lightweight dat_rmr_bind(3DAT) operation that generates rmr_context.
If the operation fails (does not return DAT_SUCCESS), the return values of rmr_handle are undefined and Consumers should not use them.
The pz_handle parameter provide Consumers a way to restrict access to an RMR by authorized connection only.
The operation was successful.
The operation failed due to resource limitations.
The pz_handle parameter is invalid.
See attributes(5) for descriptions of the following attributes:
|