Device Information Library Functions
di_path_client_next_path(3DEVINFO)
NAME
di_path_client_next_path, di_path_phci_next_path - libde-
vinfo path node traversal functionsSYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ]
#include
di_path_t di_path_client_next_path(di_node_t node node,
di_path_t path);
di_path_t di_path_phci_next_path(di_node_t node node,
di_path_t path);
PARAMETERS
node The handle to a device node in a di_init(3DEVINFO)
snapshot. For di_path_client_next_path(), node must
be a client device node. Fordi_path_phci_next_path(), node must be a pHCI device
node.path DI_PATH_NIL, or the handle to a path node in a
snapshot.DESCRIPTION
Each path node is an element in a pHCI-client matrix. The
matrix is implemented by dual linked lists: one list links path nodes related to a common client head, and the other links path nodes related to a common pHCI head.The di_path_client_next_path() function is called on a mul-
tipathing 'client' device node, where a 'client' is the child of a vHCI device node, and is associated with a specific endpoint device identity (independent of physical paths). If the path argument is NULL,di_path_client_next_path() returns the first path node asso-
ciated with the client. To walk all path nodes associatedwith a client, returned di_path_t values are fed back into
di_path_client_next_path(), via the path argument, until a
null path node is returned. For each path node,di_path_bus_addr(3DEVINFO) returns the pHCI child path node
unit-address.
The di_path_phci_next_path() function is called on a mul-
tipathing pHCI device node. If the path argument is NULL,SunOS 5.11 Last change: 15 May 2008 1
Device Information Library Functionsdi_path_client_next_path(3DEVINFO)
di_path_phci_next_path() returns the first path node associ-
ated with the pHCI. To walk all path nodes associated with apHCI, returned di_path_t values are fed back into
di_path_phci_next_path(), via the path argument, until a
null path node is returned. For each path node,di_path_client_node(3DEVINFO) provides a pointer to the
associated client device node.A device node can be a client device node of one multipath-
ing class and a pHCI device node of another class.RETURN VALUES
Upon successful completion, a handle to the next path nodeis returned. Otherwise, DI_PATH_NIL is returned and errno is
set to indicate the error.ERRORS
These functions will fail if: EINVAL One or more argument was invalid. ENOTSUP Path node information is not available in the snapshot. ENXIO The end of the path node list was reached.ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Interface Stability | Committed ||_____________________________|_____________________________|
| MT-Level | Safe |
|_____________________________|_____________________________|
SEE ALSO
di_init(3DEVINFO), di_path_bus_addr(3DEVINFO),
di_path_client_node(3DEVINFO), libdevinfo(3LIB), attri-
butes(5)SunOS 5.11 Last change: 15 May 2008 2
Device Information Library Functionsdi_path_client_next_path(3DEVINFO)
Writing Device DriversSunOS 5.11 Last change: 15 May 2008 3
Device Information Library Functionsdi_path_client_next_path(3DEVINFO)
SunOS 5.11 Last change: 15 May 2008 4