di_path_phci_next_path(3devinfo) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

di_path_phci_next_path(3devinfo)

Device Information Library Functions
                                            di_path_client_next_path(3DEVINFO)



NAME
       di_path_client_next_path, di_path_phci_next_path - libdevinfo path node
       traversal functions

SYNOPSIS
       cc [ flag... ] file... -ldevinfo [ library... ]
       #include <libdevinfo.h>

       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. For di_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 com‐
       mon pHCI head.


       The di_path_client_next_path() function is  called  on  a  multipathing
       'client'  device  node,  where a 'client' is the child of a vHCI device
       node, and is associated with a specific endpoint device identity (inde‐
       pendent   of   physical   paths).   If   the  path  argument  is  NULL,
       di_path_client_next_path() returns the first path node associated  with
       the  client.  To walk all path nodes associated with 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 multipathing pHCI
       device node. If the path  argument  is  NULL,  di_path_phci_next_path()
       returns  the first path node associated with the pHCI. To walk all path
       nodes associated with a pHCI, 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 multipathing class and
       a pHCI device node of another class.

RETURN VALUES
       Upon successful completion, a handle to the next path node is 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(7) for descriptions of the following attributes:


       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE VALUE _ Interface StabilityCommitted _ MT-LevelSafe


SEE ALSO
       di_init(3DEVINFO),                          di_path_bus_addr(3DEVINFO),
       di_path_client_node(3DEVINFO), libdevinfo(3LIB), attributes(7)


       Writing Device Drivers in Oracle Solaris 11.4



Oracle Solaris 11.4               15 May 2008
                                            di_path_client_next_path(3DEVINFO)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3