|Skip Navigation Links|
|Exit Print View|
|man pages section 3: Extended Library Functions, Volume 1 Oracle Solaris 11.1 Information Library|
- traverse libdevinfo minor nodes
cc [ flag... ] file... -ldevinfo [ library... ] #include <libdevinfo.h> int di_walk_minor(di_node_t root, const char *minor_nodetype, uint_t flag, void *arg, int (*minor_callback)(di_node_t node, di_minor_t minor, void *arg));
Pointer to caller– specific user data.
Specify 0. Reserved for future use.
The minor node visited.
A character string specifying the minor data type, which may be one of the types defined by the Solaris DDI framework, for example, DDI_NT_BLOCK. NULL matches all minor_node types. See ddi_create_minor_node(9F).
The device node with which to the minor node is associated.
Root of subtree to visit.
The di_walk_minor() function visits all minor nodes attached to device nodes in a subtree rooted at root. For each minor node that matches minor_nodetype, the caller-supplied function minor_callback() is invoked. The walk terminates immediately when minor_callback() returns DI_WALK_TERMINATE.
Upon successful completion, di_walk_minor() returns 0. Otherwise, -1 is returned and errno is set to indicate the error.
The minor_callback() function returns one of the following:
Continue to visit subsequent minor data nodes.
Terminate the walk immediately.
The di_walk_minor() function will fail if:
See attributes(5) for descriptions of the following attributes:
The di_walk_minor() function is no longer an accurate method for walking network datalink interfaces on the system. Applications should use dlpi_walk(3DLPI) instead. It has been common for applications to use di_walk_minor() to walk networking devices by passing in a minor_nodetype of DDI_NT_NET, in most cases to discover the set of DLPI devices on the system. Solaris now makes a layering distinction between networking devices (the objects displayed in the DEVICE field by dladm show-phys) and network datalink interfaces (the objects displayed by dladm show-link). Datalink interfaces are represented as the set of DLPI device nodes that applications can open by using dlpi_open(3DLPI) or by opening DLPI nodes out of the /dev/net filesystem (see filesystem(5)). The dlpi_walk(3DLPI) function is the proper function to walk these nodes.