source.h
IntroductionThe dispatch framework provides a suite of interfaces for monitoring low- level system objects (file descriptors, Mach ports, signals, VFS nodes, etc.) for activity and automatically submitting event handler blocks to dispatch queues when such activity occurs. This suite of interfaces is known as the Dispatch Source API. Functions
dispatch_source_cancelAsynchronously cancel the dispatch source, preventing any further invocation of its event handler block. ( macos( 10.6), ios( 4.0)) void dispatch_source_cancel( dispatch_source_t source); ParametersDiscussionCancellation prevents any further invocation of the event handler block for the specified dispatch source, but does not interrupt an event handler block that is already in progress. The cancellation handler is submitted to the source's target queue once the the source's event handler has finished, indicating it is now safe to close the source's handle (i.e. file descriptor or mach port). See dispatch_source_set_cancel_handler() for more information. dispatch_source_createCreates a new dispatch source to monitor low-level system objects and auto- matically submit a handler block to a dispatch queue in response to events. ( macos( 10.6), ios( 4.0)) DISPATCH_MALLOC DISPATCH_RETURNS_RETAINED dispatch_source_t dispatch_source_create( dispatch_source_type_t type, uintptr_t handle, uintptr_t mask, dispatch_queue_t _Nullable queue); Parameters
Return ValueThe newly created dispatch source. Or NULL if invalid arguments are passed. DiscussionDispatch sources are not reentrant. Any events received while the dispatch source is suspended or while the event handler block is currently executing will be coalesced and delivered after the dispatch source is resumed or the event handler block has returned. Dispatch sources are created in an inactive state. After creating the source and setting any desired attributes (i.e. the handler, context, etc.), a call must be made to dispatch_activate() in order to begin event delivery. Calling dispatch_set_target_queue() on a source once it has been activated is not allowed (see dispatch_activate() and dispatch_set_target_queue()). For backward compatibility reasons, dispatch_resume() on an inactive, and not otherwise suspended source has the same effect as calling dispatch_activate(). For new code, using dispatch_activate() is preferred. dispatch_source_get_dataReturns pending data for the dispatch source. ( macos( 10.6), ios( 4.0)) uintptr_t dispatch_source_get_data( dispatch_source_t source); ParametersReturn ValueThe return value should be interpreted according to the type of the dispatch source, and may be one of the following: DISPATCH_SOURCE_TYPE_DATA_ADD: application defined data DISPATCH_SOURCE_TYPE_DATA_OR: application defined data DISPATCH_SOURCE_TYPE_DATA_REPLACE: application defined data DISPATCH_SOURCE_TYPE_MACH_SEND: dispatch_source_mach_send_flags_t DISPATCH_SOURCE_TYPE_MACH_RECV: n/a DISPATCH_SOURCE_TYPE_MEMORYPRESSURE dispatch_source_memorypressure_flags_t DISPATCH_SOURCE_TYPE_PROC: dispatch_source_proc_flags_t DISPATCH_SOURCE_TYPE_READ: estimated bytes available to read DISPATCH_SOURCE_TYPE_SIGNAL: number of signals delivered since the last handler invocation DISPATCH_SOURCE_TYPE_TIMER: number of times the timer has fired since the last handler invocation DISPATCH_SOURCE_TYPE_VNODE: dispatch_source_vnode_flags_t DISPATCH_SOURCE_TYPE_WRITE: estimated buffer space available DiscussionThis function is intended to be called from within the event handler block. The result of calling this function outside of the event handler callback is undefined. dispatch_source_get_handleReturns the underlying system handle associated with this dispatch source. ( macos( 10.6), ios( 4.0)) uintptr_t dispatch_source_get_handle( dispatch_source_t source); ParametersReturn ValueThe return value should be interpreted according to the type of the dispatch source, and may be one of the following handles: DISPATCH_SOURCE_TYPE_DATA_ADD: n/a DISPATCH_SOURCE_TYPE_DATA_OR: n/a DISPATCH_SOURCE_TYPE_DATA_REPLACE: n/a DISPATCH_SOURCE_TYPE_MACH_SEND: mach port (mach_port_t) DISPATCH_SOURCE_TYPE_MACH_RECV: mach port (mach_port_t) DISPATCH_SOURCE_TYPE_MEMORYPRESSURE n/a DISPATCH_SOURCE_TYPE_PROC: process identifier (pid_t) DISPATCH_SOURCE_TYPE_READ: file descriptor (int) DISPATCH_SOURCE_TYPE_SIGNAL: signal number (int) DISPATCH_SOURCE_TYPE_TIMER: n/a DISPATCH_SOURCE_TYPE_VNODE: file descriptor (int) DISPATCH_SOURCE_TYPE_WRITE: file descriptor (int) dispatch_source_get_maskReturns the mask of events monitored by the dispatch source. ( macos( 10.6), ios( 4.0)) uintptr_t dispatch_source_get_mask( dispatch_source_t source); ParametersReturn ValueThe return value should be interpreted according to the type of the dispatch source, and may be one of the following flag sets: DISPATCH_SOURCE_TYPE_DATA_ADD: n/a DISPATCH_SOURCE_TYPE_DATA_OR: n/a DISPATCH_SOURCE_TYPE_DATA_REPLACE: n/a DISPATCH_SOURCE_TYPE_MACH_SEND: dispatch_source_mach_send_flags_t DISPATCH_SOURCE_TYPE_MACH_RECV: n/a DISPATCH_SOURCE_TYPE_MEMORYPRESSURE dispatch_source_memorypressure_flags_t DISPATCH_SOURCE_TYPE_PROC: dispatch_source_proc_flags_t DISPATCH_SOURCE_TYPE_READ: n/a DISPATCH_SOURCE_TYPE_SIGNAL: n/a DISPATCH_SOURCE_TYPE_TIMER: dispatch_source_timer_flags_t DISPATCH_SOURCE_TYPE_VNODE: dispatch_source_vnode_flags_t DISPATCH_SOURCE_TYPE_WRITE: n/a dispatch_source_merge_dataMerges data into a dispatch source of type DISPATCH_SOURCE_TYPE_DATA_ADD, DISPATCH_SOURCE_TYPE_DATA_OR or DISPATCH_SOURCE_TYPE_DATA_REPLACE, and submits its event handler block to its target queue. ( macos( 10.6), ios( 4.0)) void dispatch_source_merge_data( dispatch_source_t source, uintptr_t value); Parametersdispatch_source_set_cancel_handlerSets the cancellation handler block for the given dispatch source. #if (defined( 1)) ( macos( 10.6), ios( 4.0)) DISPATCH_NONNULL1 void dispatch_source_set_cancel_handler( dispatch_source_t source, dispatch_block_t _Nullable handler); #endif /* __BLOCKS__ */ ParametersDiscussionThe cancellation handler (if specified) will be submitted to the source's target queue in response to a call to dispatch_source_cancel() once the system has released all references to the source's underlying handle and the source's event handler block has returned. IMPORTANT: Source cancellation and a cancellation handler are required for file descriptor and mach port based sources in order to safely close the descriptor or destroy the port. Closing the descriptor or port before the cancellation handler is invoked may result in a race condition. If a new descriptor is allocated with the same value as the recently closed descriptor while the source's event handler is still running, the event handler may read/write data to the wrong descriptor. dispatch_source_set_cancel_handler_fSets the cancellation handler function for the given dispatch source. ( macos( 10.6), ios( 4.0)) DISPATCH_NONNULL1 void dispatch_source_set_cancel_handler_f( dispatch_source_t source, dispatch_function_t _Nullable handler); Parameters
DiscussionSee dispatch_source_set_cancel_handler() for more details. dispatch_source_set_event_handlerSets the event handler block for the given dispatch source. #if (defined( 1)) ( macos( 10.6), ios( 4.0)) DISPATCH_NONNULL1 void dispatch_source_set_event_handler( dispatch_source_t source, dispatch_block_t _Nullable handler); #endif /* __BLOCKS__ */ Parametersdispatch_source_set_event_handler_fSets the event handler function for the given dispatch source. ( macos( 10.6), ios( 4.0)) DISPATCH_NONNULL1 void dispatch_source_set_event_handler_f( dispatch_source_t source, dispatch_function_t _Nullable handler); Parameters
dispatch_source_set_registration_handlerSets the registration handler block for the given dispatch source. #if (defined( 1)) ( macos( 10.7), ios( 4.3)) DISPATCH_NONNULL1 void dispatch_source_set_registration_handler( dispatch_source_t source, dispatch_block_t _Nullable handler); #endif /* __BLOCKS__ */ ParametersDiscussionThe registration handler (if specified) will be submitted to the source's target queue once the corresponding kevent() has been registered with the system, following the initial dispatch_resume() of the source. If a source is already registered when the registration handler is set, the registration handler will be invoked immediately. dispatch_source_set_registration_handler_fSets the registration handler function for the given dispatch source. ( macos( 10.7), ios( 4.3)) DISPATCH_NONNULL1 void dispatch_source_set_registration_handler_f( dispatch_source_t source, dispatch_function_t _Nullable handler); Parameters
DiscussionSee dispatch_source_set_registration_handler() for more details. dispatch_source_set_timerSets a start time, interval, and leeway value for a timer source. ( macos( 10.6), ios( 4.0)) void dispatch_source_set_timer( dispatch_source_t source, dispatch_time_t start, uint64_t interval, uint64_t leeway); ParametersDiscussionOnce this function returns, any pending source data accumulated for the previous timer values has been cleared; the next fire of the timer will occur at 'start', and every 'interval' nanoseconds thereafter until the timer source is canceled. Any fire of the timer may be delayed by the system in order to improve power consumption and system performance. The upper limit to the allowable delay may be configured with the 'leeway' argument, the lower limit is under the control of the system. For the initial timer fire at 'start', the upper limit to the allowable delay is set to 'leeway' nanoseconds. For the subsequent timer fires at 'start' + N * 'interval', the upper limit is MIN('leeway','interval'/2). The lower limit to the allowable delay may vary with process state such as visibility of application UI. If the specified timer source was created with a mask of DISPATCH_TIMER_STRICT, the system will make a best effort to strictly observe the provided 'leeway' value even if it is smaller than the current lower limit. Note that a minimal amount of delay is to be expected even if this flag is specified. The 'start' argument also determines which clock will be used for the timer: If 'start' is DISPATCH_TIME_NOW or was created with dispatch_time(3), the timer is based on up time (which is obtained from mach_absolute_time() on Apple platforms). If 'start' was created with dispatch_walltime(3), the timer is based on gettimeofday(3). Calling this function has no effect if the timer source has already been canceled. dispatch_source_testcancelTests whether the given dispatch source has been canceled. ( macos( 10.6), ios( 4.0)) intptr_t dispatch_source_testcancel( dispatch_source_t source); ParametersReturn ValueNon-zero if canceled and zero if not canceled. Typedefs
DISPATCH_SOURCE_DECLConstants of this type represent the class of low-level system object that is being monitored by the dispatch source. Constants of this type are passed as a parameter to dispatch_source_create() and determine how the handle argument is interpreted (i.e. as a file descriptor, mach port, signal number, process identifier, etc.), and how the mask argument is interpreted. DISPATCH_SOURCE_DECL( dispatch_source) typedef const struct dispatch_source_type_s *dispatch_source_type_t; See Also
dispatch_source_mach_send_flags_ttypedef unsigned long dispatch_source_mach_send_flags_t; Constants
DiscussionType of dispatch_source_mach_send flags See Also dispatch_source_memorypressure_flags_ttypedef unsigned long dispatch_source_memorypressure_flags_t; Constants
DiscussionElevated memory pressure is a system-wide condition that applications registered for this source should react to by changing their future memory use behavior, e.g. by reducing cache sizes of newly initiated operations until memory pressure returns back to normal. NOTE: applications should NOT traverse and discard existing caches for past operations when the system memory pressure enters an elevated state, as that is likely to trigger VM operations that will further aggravate system memory pressure. See Also dispatch_source_proc_flags_ttypedef unsigned long dispatch_source_proc_flags_t; Constants
DiscussionType of dispatch_source_proc flags See Also dispatch_source_timer_flags_ttypedef unsigned long dispatch_source_timer_flags_t; Constants
DiscussionType of dispatch_source_timer flags See Also dispatch_source_type_tConstants of this type represent the class of low-level system object that is being monitored by the dispatch source. Constants of this type are passed as a parameter to dispatch_source_create() and determine how the handle argument is interpreted (i.e. as a file descriptor, mach port, signal number, process identifier, etc.), and how the mask argument is interpreted. DISPATCH_SOURCE_DECL( dispatch_source) typedef const struct dispatch_source_type_s *dispatch_source_type_t; See Also
dispatch_source_vnode_flags_ttypedef unsigned long dispatch_source_vnode_flags_t; Constants
DiscussionType of dispatch_source_vnode flags See Also Macro Definitions
DISPATCH_MACH_SEND_DEAD#define DISPATCH_MACH_SEND_DEAD 0x1 DiscussionType of dispatch_source_mach_send flags See Also DISPATCH_MEMORYPRESSURE_CRITICAL#define DISPATCH_MEMORYPRESSURE_CRITICAL 0x04 DiscussionElevated memory pressure is a system-wide condition that applications registered for this source should react to by changing their future memory use behavior, e.g. by reducing cache sizes of newly initiated operations until memory pressure returns back to normal. NOTE: applications should NOT traverse and discard existing caches for past operations when the system memory pressure enters an elevated state, as that is likely to trigger VM operations that will further aggravate system memory pressure. See Also DISPATCH_MEMORYPRESSURE_NORMAL#define DISPATCH_MEMORYPRESSURE_NORMAL 0x01 DiscussionElevated memory pressure is a system-wide condition that applications registered for this source should react to by changing their future memory use behavior, e.g. by reducing cache sizes of newly initiated operations until memory pressure returns back to normal. NOTE: applications should NOT traverse and discard existing caches for past operations when the system memory pressure enters an elevated state, as that is likely to trigger VM operations that will further aggravate system memory pressure. See Also DISPATCH_MEMORYPRESSURE_WARN#define DISPATCH_MEMORYPRESSURE_WARN 0x02 DiscussionElevated memory pressure is a system-wide condition that applications registered for this source should react to by changing their future memory use behavior, e.g. by reducing cache sizes of newly initiated operations until memory pressure returns back to normal. NOTE: applications should NOT traverse and discard existing caches for past operations when the system memory pressure enters an elevated state, as that is likely to trigger VM operations that will further aggravate system memory pressure. See Also DISPATCH_PROC_EXEC#define DISPATCH_PROC_EXEC 0x20000000 DiscussionType of dispatch_source_proc flags See Also DISPATCH_PROC_EXIT#define DISPATCH_PROC_EXIT 0x80000000 DiscussionType of dispatch_source_proc flags See Also DISPATCH_PROC_FORK#define DISPATCH_PROC_FORK 0x40000000 DiscussionType of dispatch_source_proc flags See Also DISPATCH_PROC_SIGNAL#define DISPATCH_PROC_SIGNAL 0x08000000 DiscussionType of dispatch_source_proc flags See Also DISPATCH_SOURCE_TYPE_DATA_ADD#define DISPATCH_SOURCE_TYPE_DATA_ADD DiscussionA dispatch source that coalesces data obtained via calls to dispatch_source_merge_data(). An ADD is used to coalesce the data. The handle is unused (pass zero for now). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_DATA_OR#define DISPATCH_SOURCE_TYPE_DATA_OR DiscussionA dispatch source that coalesces data obtained via calls to dispatch_source_merge_data(). A bitwise OR is used to coalesce the data. The handle is unused (pass zero for now). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_DATA_REPLACEDiscussionA dispatch source that tracks data obtained via calls to dispatch_source_merge_data(). Newly obtained data values replace existing data values not yet delivered to the source handler A data value of zero will cause the source handler to not be invoked. The handle is unused (pass zero for now). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_MACH_RECV#define DISPATCH_SOURCE_TYPE_MACH_RECV DiscussionA dispatch source that monitors a Mach port for pending messages. The handle is a Mach port with a receive right (mach_port_t). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_MACH_SEND#define DISPATCH_SOURCE_TYPE_MACH_SEND DiscussionA dispatch source that monitors a Mach port for dead name notifications (send right no longer has any corresponding receive right). The handle is a Mach port with a send or send-once right (mach_port_t). The mask is a mask of desired events from dispatch_source_mach_send_flags_t. DISPATCH_SOURCE_TYPE_MEMORYPRESSURE#define DISPATCH_SOURCE_TYPE_MEMORYPRESSURE \ (&_dispatch_source_type_memorypressure) DiscussionA dispatch source that monitors the system for changes in memory pressure condition. The handle is unused (pass zero for now). The mask is a mask of desired events from dispatch_source_memorypressure_flags_t. DISPATCH_SOURCE_TYPE_PROC#define DISPATCH_SOURCE_TYPE_PROC DiscussionA dispatch source that monitors an external process for events defined by dispatch_source_proc_flags_t. The handle is a process identifier (pid_t). The mask is a mask of desired events from dispatch_source_proc_flags_t. DISPATCH_SOURCE_TYPE_READ#define DISPATCH_SOURCE_TYPE_READ DiscussionA dispatch source that monitors a file descriptor for pending bytes available to be read. The handle is a file descriptor (int). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_SIGNAL#define DISPATCH_SOURCE_TYPE_SIGNAL DiscussionA dispatch source that monitors the current process for signals. The handle is a signal number (int). The mask is unused (pass zero for now). DISPATCH_SOURCE_TYPE_TIMER#define DISPATCH_SOURCE_TYPE_TIMER DiscussionA dispatch source that submits the event handler block based on a timer. The handle is unused (pass zero for now). The mask specifies which flags from dispatch_source_timer_flags_t to apply. DISPATCH_SOURCE_TYPE_VNODE#define DISPATCH_SOURCE_TYPE_VNODE DiscussionA dispatch source that monitors a file descriptor for events defined by dispatch_source_vnode_flags_t. The handle is a file descriptor (int). The mask is a mask of desired events from dispatch_source_vnode_flags_t. DISPATCH_SOURCE_TYPE_WRITE#define DISPATCH_SOURCE_TYPE_WRITE DiscussionA dispatch source that monitors a file descriptor for available buffer space to write bytes. The handle is a file descriptor (int). The mask is unused (pass zero for now). DISPATCH_TIMER_STRICT#define DISPATCH_TIMER_STRICT 0x1 DiscussionType of dispatch_source_timer flags See Also DISPATCH_VNODE_ATTRIB#define DISPATCH_VNODE_ATTRIB 0x8 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_DELETE#define DISPATCH_VNODE_DELETE 0x1 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_EXTEND#define DISPATCH_VNODE_EXTEND 0x4 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_FUNLOCK#define DISPATCH_VNODE_FUNLOCK 0x100 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_LINK#define DISPATCH_VNODE_LINK 0x10 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_RENAME#define DISPATCH_VNODE_RENAME 0x20 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_REVOKE#define DISPATCH_VNODE_REVOKE 0x40 DiscussionType of dispatch_source_vnode flags See Also DISPATCH_VNODE_WRITE#define DISPATCH_VNODE_WRITE 0x2 DiscussionType of dispatch_source_vnode flags See Also |