21 object with a port. Only objects associated with a particular port are
22 able to generate events that can be retrieved using port_get(3C) or
23 port_getn(3C). The delivery event has its portev_user member set to the
24 value specified in the user parameter. If the specified object is
25 already associated with the specified port, the port_associate()
26 function serves to update the events and user arguments of the
27 association. The port_dissociate() function removes the association of
28 an object with a port.
29
30
31 The objects that can be associated with a port by way of the
32 port_associate() function are objects of type PORT_SOURCE_FD and
33 PORT_SOURCE_FILE. Objects of other types have type-specific association
34 mechanisms. A port_notify_t structure, defined in <port.h>, is used to
35 specify the event port and an application-defined cookie to associate
36 with these event sources. See port_create(3C) and signal.h(3HEAD).
37
38
39 The port_notify_t structure contains the following members:
40
41 int portntfy_port; /* bind request(s) to port */
42 void *portntfy_user; /* user defined cookie */
43
44
45
46 Objects of type PORT_SOURCE_FD are file descriptors. The event types
47 for PORT_SOURCE_FD objects are described in poll(2). At most one event
48 notification will be generated per associated file descriptor. For
49 example, if a file descriptor is associated with a port for the
50 POLLRDNORM event and data is available on the file descriptor at the
51 time the port_associate() function is called, an event is immediately
52 sent to the port. If data is not yet available, one event is sent to
53 the port when data first becomes available.
54
55
56 When an event for a PORT_SOURCE_FD object is retrieved, the object no
57 longer has an association with the port. The event can be processed
58 without the possibility that another thread can retrieve a subsequent
59 event for the same object. After processing of the file descriptor is
60 completed, the port_associate() function can be called to reassociate
61 the object with the port.
62
336
337
338
339
340 +--------------------+-----------------+
341 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
342 +--------------------+-----------------+
343 |Architecture | all |
344 +--------------------+-----------------+
345 |Interface Stability | Committed |
346 +--------------------+-----------------+
347 |MT-Level | Safe |
348 +--------------------+-----------------+
349
350 SEE ALSO
351 rctladm(1M), poll(2), setrctl(2), port_alert(3C), port_create(3C),
352 port_get(3C), port_send(3C), signal.h(3HEAD), attributes(5)
353
354
355
356 November 9, 2007 PORT_ASSOCIATE(3C)
|
21 object with a port. Only objects associated with a particular port are
22 able to generate events that can be retrieved using port_get(3C) or
23 port_getn(3C). The delivery event has its portev_user member set to the
24 value specified in the user parameter. If the specified object is
25 already associated with the specified port, the port_associate()
26 function serves to update the events and user arguments of the
27 association. The port_dissociate() function removes the association of
28 an object with a port.
29
30
31 The objects that can be associated with a port by way of the
32 port_associate() function are objects of type PORT_SOURCE_FD and
33 PORT_SOURCE_FILE. Objects of other types have type-specific association
34 mechanisms. A port_notify_t structure, defined in <port.h>, is used to
35 specify the event port and an application-defined cookie to associate
36 with these event sources. See port_create(3C) and signal.h(3HEAD).
37
38
39 The port_notify_t structure contains the following members:
40
41 int portnfy_port; /* bind request(s) to port */
42 void *portnfy_user; /* user defined cookie */
43
44
45
46 Objects of type PORT_SOURCE_FD are file descriptors. The event types
47 for PORT_SOURCE_FD objects are described in poll(2). At most one event
48 notification will be generated per associated file descriptor. For
49 example, if a file descriptor is associated with a port for the
50 POLLRDNORM event and data is available on the file descriptor at the
51 time the port_associate() function is called, an event is immediately
52 sent to the port. If data is not yet available, one event is sent to
53 the port when data first becomes available.
54
55
56 When an event for a PORT_SOURCE_FD object is retrieved, the object no
57 longer has an association with the port. The event can be processed
58 without the possibility that another thread can retrieve a subsequent
59 event for the same object. After processing of the file descriptor is
60 completed, the port_associate() function can be called to reassociate
61 the object with the port.
62
336
337
338
339
340 +--------------------+-----------------+
341 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
342 +--------------------+-----------------+
343 |Architecture | all |
344 +--------------------+-----------------+
345 |Interface Stability | Committed |
346 +--------------------+-----------------+
347 |MT-Level | Safe |
348 +--------------------+-----------------+
349
350 SEE ALSO
351 rctladm(1M), poll(2), setrctl(2), port_alert(3C), port_create(3C),
352 port_get(3C), port_send(3C), signal.h(3HEAD), attributes(5)
353
354
355
356 August 8, 2015 PORT_ASSOCIATE(3C)
|