/* $Source: runtime/gasnet/other/firehose/firehose.h $ * $Date: Sat, 28 May 2005 02:53:07 -0700 $ * $Revision: 1.4.1.5 $ * Description: Public Header file * Copyright 2004, Christian Bell * Terms of use are as specified in license.txt */ #ifndef FIREHOSE_H #define FIREHOSE_H #include #include struct _firehose_private_t; typedef struct _firehose_private_t firehose_private_t; #if ((defined(FIREHOSE_PAGE) && defined(FIREHOSE_REGION)) || \ (!defined(FIREHOSE_PAGE) && !defined(FIREHOSE_REGION)) || \ (defined(FIREHOSE_PAGE) && defined(FIREHOSE_CLIENT_T))) #error Only define one of FIREHOSE_PAGE or FIREHOSE_REGION. Make sure \ FIREHOSE_CLIENT_T is only defined if FIREHOSE_REGION is defined. #endif #define FIREHOSE_API_VERSION 0x101 /* The firehose request type is returned as a read-only type from * firehose local and remote pin functions. Based on the address and * length requested by the pin operation, this return type describes a * region that is a superset of the one requested, namely the start * address can be lower and the length of the region can be larger. * The returned base address ('addr' field) is always aligned on a * page boundary and the length ('len' field) is always a multiple of * page size. * * Once returned to the client, this type is read-only. Copies of * this type are never kept around in hash tables. On all the * firehose_*_pin functions, clients can pass a pointer to their own * allocated request_t or NULL which causes firehose to use its own * request_t allocation. If a request_t is to be returned and the * client passed a non-null request_t pointer, firehose guarentees * that the returned pointer will equal the one the client passed. */ typedef struct _firehose_request_t { uint16_t flags; /* internal -- opaque to client */ gasnet_node_t node; uintptr_t addr; size_t len; /* internal -- opaque to client */ firehose_private_t *internal; #ifdef FIREHOSE_CLIENT_T /* For CLIENT use, defined in firehose_fwd.h Useful for * keys/handles and similar transport-specific data Note that * this is included inline, not as a reference. */ firehose_client_t client; #endif } firehose_request_t; /* The firehose region type contains the necessary minimal information * required to describe a pinned region. The type is used both by the * client-supplied firehose_move_callback to pin and unpin regions and * internally by the firehose algorithm to disconnect old firehoses * and reconnect new ones. * * The address field is aligned on a page boundary and the length * field is a multiple of page size. * * If the network requires client data to be attached to each pinning * operation, the client field should be filled in. */ typedef struct _firehose_region_t { uintptr_t addr; size_t len; #ifdef FIREHOSE_CLIENT_T firehose_client_t client; #endif } firehose_region_t; /* The firehose information type contains information relative to the * the limits of system and network-related available to firehose. * The type is returned at initialization and contains limit * information the client can query at initialization. The limit * values are calculated by the firehose interface according to the * following parameters: * 1. Maximum amount of globally pinnable memory * 2. Maximum amount of regions that may be created * 3. Environment variables to control firehose (see * GASNET_FIREHOSE_ environment variables below). * 4. gasnet_AMMaxMedium() as implemented by the underlying gasnet * core API. * 5. The size of firehose_remotecallback_args_t. * * The values returned by firehose_info_t are established at * initialization. Typically, a client will use these limits in order * to determine the size of the largest remote and/or local region * that can be requested through the firehose interface. See the * section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for more * information. */ typedef struct _firehose_info_t { /* Local and remote maximum region sizes that can be requested * through one of the firehose_*_pin functions */ size_t max_RemotePinSize; size_t max_LocalPinSize; /* Local and remote maximum number of active regions */ size_t max_RemoteRegions; size_t max_LocalRegions; } firehose_info_t; /********************************************************************/ /* CLIENT-SUPPLIED CALLBACKS */ /********************************************************************/ /* The following callbacks are to be implemented by the client. * * Each of the callbacks should return 0 on success and non-zero on * failure. Firehose will exit with a fatal error if the callback * returns non-zero. * *************************** * FIREHOSE REMOTE CALLBACK *************************** * This callback can be invoked on the remote node when the firehose * library has completed a firehose move on the requested node. * Remote pin operations that require firehose moves can allow the * client to run a callback after the completion of the move operation * and before the firehose reply. * * When enabled for a move request, the callback is never run within * an AM handler context unless the client defines * FIREHOSE_REMOTE_CALLBACK_IN_HANDLER in which case the remote * callback will be executed within the firehose request handler after * the move is complete and before the firehose reply. In either * case, the callback must be thread-safe. * * A client enables the remote callback for a move operation by * setting the FIREHOSE_FLAG_ENABLE_REMOTE_CALLBACK bit in the * remote pin flags parameter. See firehose_remote_pin() and * firehose_try_remote_pin() functions. * * AM-handler context: Runs within AM handler if (and only if) client * defines FIREHOSE_REMOTE_CALLBACK_IN_HANDLER. * * Returns: 0 on success, non-zero on failure. */ extern int firehose_remote_callback(gasnet_node_t node, const firehose_region_t *pin_list, size_t num_pinned, firehose_remotecallback_args_t *args); /************************* * FIREHOSE MOVE CALLBACK ************************* * This callback is invoked when the firehose library has determined * the need to pin and/or unpin one or many regions and is a * synchronous (blocking) operation. If there are regions to be * unpinned, the unpin call should be executed prior to the pin call. * For some networks, it may be possible to use a repin operation, * allowing pinning resources to be used more effectively. * * If the client has defined FIREHOSE_CLIENT_T, the function should * fill-in any neccesary data in the 'client' field of the 'pin_list' * of firehose regions, which will be copied back to the node owning * the firehose (could be the local node) in an AMReplyMedium(). * Changes to the client type in the region type will be reflected in * the request type once the move callback completes. * * AM-handler context: May run in AM handler context * * Returns: 0 on success, non-zero on failure. */ extern int firehose_move_callback(gasnet_node_t node, const firehose_region_t *unpin_list, size_t unpin_num, firehose_region_t *pin_list, size_t pin_num); #ifdef FIREHOSE_BIND_CALLBACK /* This prototype is for a callback implemented by the CLIENT iff the * client defines FIREHOSE_BIND_CALLBACK. * * This callback is invoked by the firehose library when the node * initiating a move operation has received a reply to the list of * regions to be pinned. It is up to the client to make sure * (possibly by way of a firehose_client_t) that any metadata required * to bind to a remote region is part of the region type. * * AM-handler context: May run in AM handler context */ extern int firehose_bind_callback(gasnet_node_t node, firehose_region_t *bind_list, size_t bind_num); #endif #ifdef FIREHOSE_UNBIND_CALLBACK /* This prototype is for a callback implemented by the CLIENT iff the * client defines FIREHOSE_UNBIND_CALLBACK. * * This callback is invoked when the firehose library selects one or * many regions to be unpinned. It is up to the client to make sure * (possibly by way of a firehose_client_t) that any metadata required * to unbind a local node to a remote region is part of the region * type. * * AM-handler context: May run in AM handler context */ extern int firehose_unbind_callback(gasnet_node_t node, const firehose_region_t *unbind_list, size_t unbind_num); #endif #ifdef FIREHOSE_EXPORT_CALLBACK /* This prototype is for a callback implemented by the CLIENT iff the * client defines FIREHOSE_EXPORT_CALLBACK. * * This callback is invoked by the firehose library when a request to * pin a local region is received. It is up to the client to make * sure (possibly by way of a firehose_client_t) that any metadata * required to export a region to a remote node is part of the region * type. * * AM-handler context: May run in AM handler context */ extern int firehose_export_callback(gasnet_node_t node, firehose_region_t *export_list, size_t export_num); #endif #ifdef FIREHOSE_UNEXPORT_CALLBACK /* This prototype is for a callback implemented by the CLIENT iff the * client defines FIREHOSE_UNEXPORT_CALLBACK. * * This callback is invoked by the firehose library when a request to * unpin a local region is received. It is up to the client to make * sure (possibly by way of a firehose_client_t) that any metadata * required to export a region to a remote node is part of the region * type. * * AM-handler context: May run in AM handler context */ extern int firehose_unexport_callback(gasnet_node_t node, const firehose_region_t *unexport_list, size_t unexport_num); #endif /********************************************************************/ /* FIREHOSE INITIALIZATION AND RUNTIME */ /********************************************************************/ /* The following functions must be used at initialization and * termination of the firehose interface, as well as at runtime for * the firehose progress engine (firehose_poll()). * *********************************** * Firehose AM Handler registration *********************************** * This function must be called by the client prior to initializing * the firehose interface in order to register firehose AM handlers. * The function returns an array of gasnet_handlerentry_t terminated * with a gasnet_handlerentry_t entry containing a NULL function * pointer. * * Upon calling firehose_get_handlertable(), clients should loop over * the array of gasnet_handlerentry_t and fill in a valid * gasnet_handler_t index for each function pointer. At firehose * initialization, a check is made to make sure each function pointer * has been assigned a useable index number. */ extern gasnet_handlerentry_t * firehose_get_handlertable(); /************************** * Firehose Initialization ************************** * Called to setup the firehose tables and data structures. This call * must be executed once gasnet has registered the segment and all * core and extended AM handlers. Typically, the firehose init call * is done as part of the last step before gasnet_attach's final * bootstrap barrier. Additionally, the client must have registered * firehose AM handlers by querying firehose_gethandlers() prior to * calling firehose_init(). * * If a list of prepinned page-aligned regions is passed, firehose * initializes the reference count for these regions to 1 (which * guarentees that these regions remain pinned). It is up to the * client to make sure that these regions are pinned prior to calling * firehose_init. These regions may lie anywhere in the address space * -- in or out of the GASNet segment, in stack-adressable memory, * etc. The client is free to issue additional firehose_local_* and * firehose_remote_* calls on these regions. The memory for the * regions list is owned by the client and may safely be reused or * freed after firehose_init() returns. * * Firehose separates pinning resources using two parameters: * 1. The 'maximum_pinnable_memory' is the upper bound for the * firehose 'M' parameter and must be the largest global minimum * of the largest amount of memory that can be pinned by each * node. This value should be a fraction of the amount of * physical memory a single process can pin and it is up to the * client to implement a network specific exchange operation to * find the global minimum. * 2. The 'maximum_regions' is the upper bound for the firehose * 'R' parameter and must be the largest global minimum of * the largest amount of regions that can be allocated by each * node. * * Along with the global minimum requirement, each thread is required * to pass the same 'max_pinnable_memory' and 'max_regions' values to * the function. Setting either value to zero removes the constraints * associated to the count. In other words, the firehose algorithm * can consider there to be no contraints on the amount of pinned * memory or maximum regions if either value is set to 0. */ extern void firehose_init(uintptr_t max_pinnable_memory, size_t max_regions, const firehose_region_t *prepinned_regions, size_t num_reg, uint32_t flags, firehose_info_t *info); /* Environment variables used in firehose initialization * * Although firehose is informed of job-wide resource limitations * through its initialization function, users can control firehose * parameters through environment variables. * * Except where noted, the numerical values are assumed to be base-2 * megabytes. For these environement variables, a suffix of 'GB' can * be appended for (base-2) gigabytes or 'KB' for (base-2) kilobytes * ('MB' will simply be ignored if it is specified). * * GASNET_FIREHOSE_M establishes, in megabytes, the number of * firehose buckets each node partitions across all * nodes. This is limited by the * 'max_pinnable_memory' parameter. * * GASNET_FIREHOSE_R establishes, in units of regions, the maximum * number of regions each node partitions across all * nodes. This value is ignored if 'max_regions' is * 0. * * GASNET_FIREHOSE_MAXVICTIM_M limits, in megabytes, the length of * the FIFO queue and hence the amount of * inactive pinned regions. This allows * firehose to ammortize the number * of unpin operations. * * GASNET_FIREHOSE_MAXVICTIM_R limits, in units of regions, the * length of the FIFO queue and hence the * amount of inactive pinned regions. * This value is ignored if 'max_regions' * is 0. * * GASNET_FIREHOSE_MAXREGION_SIZE limits, in megabytes, the length * of the largest possible region to be * managed by firehose. * * NOTE: firehose_init() will fail at initialization if * (max_pinnable_memory != 0) && * (GASNET_FIREHOSE_M+GASNET_FIREHOSE_MAXVICTIM_M > max_pinnable_memory) * or if * (max_regions != 0) && * (GASNET_FIREHOSE_R+GASNET_FIREHOSE_MAXVICTIM_R > max_regions) * * Failing to set these environment variables causes metadata for the * maximum amount of memory and regions to be allocated at * initialization. */ /* Flags passed to firehose initialization * * FIREHOSE_INIT_FLAG_LOCAL_ONLY * Though firehose is designed to address the management of remote * pinning resources, it is also usefull for managing purely local * dynamic pinnings (for instance when the GASNet conduit has * prepinned the segment and only needs to dynamically pin local * out-of-segment memory). * When firehose_init() is passed FIREHOSE_INIT_FLAG_LOCAL_ONLY, * firehose will manage only local pinnings. All resources indicated * by the max_pinnable_memory and max_regions arguments will be used * for the victim FIFO (local only firehoses), subject to override by * the corresponding environment variables. Tables used to track * remote firehoses will not be allocated. If this flag is passed, it * is an error to call firehose_remote_pin(), firehose_try_remote_pin() * or firehose_partial_remote_pin. The max_RemotePinSize and * max_RemoteRegions values in the firehose_info_t will be zero. * CURRENTLY ONLY IMPLEMENTED FOR FIREHOSE-REGION * * FIREHOSE_INIT_FLAG_UNPIN_ON_FINI * If this flag is set, firehose_fini() will unpin all memory it * has pinned (excludes pre-pinned regions passed to firehose_init()). * This may add significantly to the exit cost, and so should be used * only if you believe that the system does not cleanup properly when * a process exits. * CURRENTLY ONLY IMPLEMENTED FOR FIREHOSE-REGION */ #define FIREHOSE_INIT_FLAG_LOCAL_ONLY 0x01 #define FIREHOSE_INIT_FLAG_UNPIN_ON_FINI 0x02 /************************ * Firehose Finalization ************************ * * Called to cleanup and terminate firehose. This call is * non-collective and should be called as part of gasnet_exit(). * */ extern void firehose_fini(void); /******************* * Firehose Polling ******************* * * Called to make progress on the outstanding firehose messages. This * call is thread-safe and may be called concurrently on different * threads outside a handler context. * * Client implementors should remember to call firehose_poll() after * servicing AMReply handlers. * * AM-handler context: Cannot be run in a handler. */ #if defined(FIREHOSE_REMOTE_CALLBACK_IN_HANDLER) && \ defined(FIREHOSE_COMPLETION_IN_HANDLER) #define firehose_poll() #else extern void firehose_poll(void); #endif /************************* * Firehose Segment Sizes ************************* * * Clients can retrieve M and Maxvictim values if firehose is given * a maximum amount of pinnable memory. * * AM-handler context: Irrelevent, but safe. * */ extern void firehose_get_params(uintptr_t max_pinnable_memory, uintptr_t *M, uintptr_t *Maxvictim); /********************************************************************/ /* FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE) */ /********************************************************************/ /* * The following semantics are shared by all the firehose pinning * functions, firehose_*_pin(): * * The firehose pinning functions cannot be called from within an * AM handler context. * * All the pinning functions take a request_t pointer as an * argument, and either return one, or pass one to a completion * callback. * If this "req" argument is not NULL then upon success: * + The firehose_*_pin() function will use this storage for its * result, and the value returned (or passed to a callback) will * be this same pointer. * + The client maintains ownership of this storage and is * responsible for any free() (or similar call) required, but * not before the corresponding firehose_release(). * If this "req" argument is NULL then upon success: * + The firehose firehose_*_pin() function will allocate storage * necessary for the request_t to be returned (or passed). * + The balancing call to firehose_release() will recover the * storage. * * The regions returned (or pased to completion callbacks) by the * firehose_*_pin() functions may lie partly outside of the requested * region. Specifically, the start address can be lower than requested * and/or the end of the region can be higher than requested. * * In order to RDMA to/from any local or remote memory, a client must * "own" a request_t at each end (except where the transport may have * weaker requirements on local memory or pre-pinned pages are used * without going through firehose). A request_t is "owned" by the * client from the time it is returned from a firehose_*_pin() function * or passed to a completion callback, until the time the client calls * firehose_release() on the request_t. * * The region limits in firehose_info_t can be described in terms of the * union of the local or remote request_t's owned by a client at any * given instant. * + max_RemoteRegions - the maximum number of distinct regions * pinned by the union of all the request_t's which reference any * given remote node. * + max_LocalRegions - the maximum number of distinct regions pinned * by the union of all the request_t's referencing the local node. * If any of these values is zero then that limit is not imposed. * * The pin size limit in firehose_info_t are: * + max_RemotePinSize - the maximum value of the 'len' argument to the * remote pinning functions firehose_remote_pin() and * firehose_try_remote_pin(). * + max_LocalPinSize - the maximum value of the 'len' argument to the * local pinning functions firehose_local_pin() and * firehose_try_local_pin(). * * The 'len' argument to the firehose_partial_*_pin() functions is not * limited by the max_*PinSize parameters. However, the request_t's * they return will have length bounded by the appropriate max_*PinSize. * * Note that for all the firehose_*_pin functions the pair (addr, len) * must be well formed, meaning that the closed interval [addr, * addr + (len-1)] must not "wrap around" the address space. * * Let an "operation" denote the collection of request_t's owned by a * client such that they will eventually reach firehose_release() * independent of any other calls to firehose_*_pin() functions. (A * typical example of an operation might include one local request_t * and one remote request_t to be used as the source and destination * of an GET or PUT). See the paragraphs below on deadlock avoidance * for restrictions on the request_t's that can belong to an operation. * * The client must ensure that every operation can make progress * toward firehose_release(), independent of any other operation. In * particular, when all the request_t's to be owned by an operation * have been acquired, some action must be taken (such as * starting/enqueing RDMA) which will lead to the eventual * firehose_release() of the operation's request_t's. This step must * be taken before the thread initiating the operation can make calls * to firehose_local_pin() or firehose_remote_pin() for the next * operation, since these two calls might block awaiting release of * the resources used by the previous operation. For the purpose of * this rule, submitting a callback argument to firehose_remote_pin() * is sufficient, even though the callback may not run until a later * time (provided, of course, that the callback will make progress * toward the release). To ensure progess is made, clients of * firehose are guaranteed that firehose_local_pin() and * firehose_remote_pin() will call gasnet_AMPoll() while they are * awaiting release of resources. * * A potential deadlock can occur in a situation such as this: * thread0: firehose_local_pin(); firehose_remote_pin(nodeN); * thread1: firehose_remote_pin(nodeN); firehose_local_pin(); * If the available resources are sufficient to satisfy the first pin * request from each thread, but not sufficient to simultaneously * satisfy the second pin request from either thread, then a deadlock * will occur. If resources are limited enough, then the same sort * of deadlock is possible with a single thread as follows: * thread0: firehose_local_pin(); firehose_local_pin(); * Note that in both examples, if the second call(s) had been made to * firehose_try_*_pin() or firehose_partial_*_pin(), then deadlock * would not have been possible (since these calls return immediately * regardless of whether the requested memory is already pinned). * * To avoid these deadlocks, clients should follow these recommendations: * 1) Pick a precedence for pinning. If operations always consist of * at most one remote request_t, then this precedence will be either * "local-over-remote" or "remote-over-local". If operations can * include request_t's on multiple remote nodes then the precedence * must be a total order over the nodes. Though the order need not * be the same on every node, every thread on a given node must abide * by the same precedence. * 2) Once an operation owns a request_t on a given node it may not * make calls to firehose_local_pin() or firehose_remote_pin() for * any node with equal or higher precedence, because these calls could * potentially block waiting for resources which will never become * available. * 3) Calls which cannot block awaiting resources (firehose_try_*_pin() * and firehose_partial_*_pin()) are permitted in any order. However, * once one returns a request_t the client must observe rule #2. * * The recommended precedence is "remote-over-local", meaning that a * typical operation will call firehose_remote_pin() and * firehose_local_pin() in that order. This is recommended because of * the potential for performing any required network round trip and * pinning by the remote node while concurrently executing the local * pin request. * * The calls firehose_try_*_pin() and firehose_partial_*_pin() will not * cause memory to become pinned, nor will they initiate network traffic * to determine if remote memory has previously been pinned. They only * return success when the request can be satisfied based on local * knowledge of what memory is already pinned. For this reason, spin * polling on these functions is not recommended. */ /********************************************************************/ /* FIREHOSE LOCAL PINNING FUNCTIONS */ /********************************************************************/ /* * ********************* * Firehose Local Pin ********************* * Called to request local pinning of a specified region. * The return value will be non-null on success. * * This is an immediate operation, meaning no network communication is * required to complete the operation, and all side effects have * occured before this call returns. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_local_pin(uintptr_t addr, size_t len, firehose_request_t *req); /************************* * Firehose Try Local Pin ************************* * Called to find an existing local pinning of a specified region. * If the requested region is already pinned, a corresponding request * type is returned. If the region covered by (addr, addr+len) is not * pinned, the function returns NULL. * * This is an immediate operation, meaning no network communication is * required to complete the operation, and all side effects have occured * before this call returns. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_try_local_pin(uintptr_t addr, size_t len, firehose_request_t *req); /***************************** * Firehose Local Partial Pin ***************************** * Called to request a (potentially) partial local pinning operation. * The call returns with a valid request type if any portion of the * requested region is already pinned. Only if no portion of the * requested region is already pinned does the call return NULL. * * This is an immediate operation, meaning no network communication is * required to complete the operation, and all side effects have occured * before this call returns. * * When multiple pinned regions intersect the requested region, then * it is guaranteed that the region returned will include the page with * the lowest address among all pinned pages in the requested region. * However, the choice among multiple regions which include this lowest * pinned page is implementation-specific. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_partial_local_pin(uintptr_t addr, size_t len, firehose_request_t *req); /********************************************************************/ /* FIREHOSE REMOTE PINNING FUNCTIONS */ /********************************************************************/ /* Remote pin functions may or may not require a network roundtrip. * In the case where a roundtrip is required to move firehoses, a * completion callback is used to acknowledge placement of new * firehoses. * * It is invalid to request a remote pin with the local node number as * a destination node. * * Remote memory regions must fall within the GASNet segment and/or * the set of pages that are pinned locally on the target node * (including both pre-pinned pages and pages pinned via one of the * firehose local pin functions). * ******************* * Remote Pin flags ******************* * Remote pin request behaviour may be additionally controlled through * options set through the remote pin 'flags' parameter. The flags * are described below as * * FIREHOSE_FLAG_RETURN_IF_PINNED * If set, causes firehose_remote_pin() to return a valid * request_t pointer to the caller if the region is pinned * * FIREHOSE_FLAG_ENABLE_REMOTE_CALLBACK * If set, executes a callback on the remote node once the firehose * move is completed. */ #define FIREHOSE_FLAG_RETURN_IF_PINNED 0x01 #define FIREHOSE_FLAG_ENABLE_REMOTE_CALLBACK 0x02 /************************** * firehose_completed_fn_t ************************** * Type for function called after firehose placement is acknowledged * on the node initiating the firehose move. * * The callback is never run within an AM handler context unless the * client defines FIREHOSE_COMPLETION_IN_HANDLER in which case the * completion callback will be executed from within the firehose reply * handler. In either case, the callback must be thread-safe and * firehose makes no guarentees as to what thread the callback is run * on (which means the callback can run a thread different from the * thread that initiated the operation). * * The callback is run with a context pointer passed into one of the * remote pin functions and the request_t describes the remote region * that was successfully pinned. The 'allLocalHit' parameter is set * to non-zero if the remote pin operation could be successfully * completed without requiring any firehose moves (network roundtrips). * Thus if 'allLocalHit' is non-zero, any callback requested by the flag * FIREHOSE_FLAG_ENABLE_REMOTE_CALLBACK has NOT run on the remote node. * * AM-handler context: Runs within AM handler if (and only if) client * defines FIREHOSE_COMPLETION_IN_HANDLER. */ typedef void (*firehose_completed_fn_t) (void *context, const firehose_request_t *req, int allLocalHit); /********************** * Firehose Remote Pin ********************** * Called to request unconditional remote pinning of a specified region. * This call will complete in two different manners, depending on the * presence of FIREHOSE_FLAG_RETURN_IF_PINNED in the "flags" argument. * When FIREHOSE_FLAG_RETURN_IF_PINNED is set and the requested region * is already pinned, a corresponding region_t is returned without * invoking the supplied completion callback. In all other cases, the * return value is NULL, and the the supplied completion callback will * be invoked on the local node with the supplied context pointer. * * In the cases which result in invoking the supplied completion * callback, it is not specified when or in what thread the callback * will run. In particular, if the requested region is already pinned * and FIREHOSE_FLAG_RETURN_IF_PINNED is not set, it is not guaranteed * that the callback will run before firehose_remote_pin() returns. * * It is invalid to call this function with the local node number as * a destination node. * * If FIREHOSE_FLAG_ENABLE_REMOTE_CALLBACK is set, the client must pass * as 'remote_args', a valid pointer to type remotecallback_args_t as * defined in firehose_fwd.h. The contents of this type is copied over * in the firehose move (if one is requred) and passed to the remote * callback when firehose_remote_callback() is invoked. The contents * of 'remote_args' are copied before firehose_remote_pin() returns, * making the memory reusable immediately. If the request can be * satisfied from local tables, no network communication will take * place. In that case, the remote callback is NOT run. If the * flag FIREHOSE_FLAG_RETURN_IF_PINNED is set, this case is indicated * by a non-NULL return value. If FIREHOSE_FLAG_RETURN_IF_PINNED is * not set, a non-zero value of 'allLocalHit' passed to the completion * callback indicates the remote callback was not run. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_remote_pin(gasnet_node_t node, uintptr_t addr, size_t len, uint32_t flags, firehose_request_t *req, firehose_remotecallback_args_t *remote_args, firehose_completed_fn_t callback, void *context); /************************** * Firehose Remote Try Pin ************************** * Called to find an existing remote pinning of a specified region. * If the requested region is already pinned, a corresponding request * type is returned. If the region covered by (addr, addr+len) is not * pinned, the function returns NULL. * * This is an immediate operation, meaning no network communication is * required to complete the operation, and all side effects have occured * before this call returns. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_try_remote_pin(gasnet_node_t node, uintptr_t addr, size_t len, uint32_t flags, firehose_request_t *req); /****************************** * Firehose Remote Partial Pin ****************************** * Called to request a (potentially) partial remote pinning operation. * The call returns with a valid request type if any portion of the * requested region is already pinned. Only if no portion of the * requested region is already pinned does the call return NULL. * * This is an immediate operation, meaning no network communication is * required to complete the operation, and all side effects have occured * before this call returns. * * When multiple pinned regions intersect the requested region, then * it is guaranteed that the region returned will include the page with * the lowest address among all pinned pages in the requested region. * However, the choice among multiple regions which include this lowest * pinned page is implementation-specific. * * See the section "FIREHOSE PINNING FUNCTIONS (LOCAL & REMOTE)" for the * use of the "req" argument, and additional semantics common to all * firehose_*_pin() functions. * * AM-handler context: Cannot be run in a handler. */ extern const firehose_request_t * firehose_partial_remote_pin(gasnet_node_t node, uintptr_t addr, size_t len, uint32_t flags, firehose_request_t *req); /********************************************************************/ /* FIREHOSE RELEASE */ /********************************************************************/ /* Both local and remote pin requests must be balanced with a call to * firehose release. It indicates that the use of the indicated * 'num_requests' requests for RDMA has completed. This is a * synchronous (blocking) operation. * * The supplied regions can be local or remote. * * AM-handler context: May be called in an AM handler context * */ extern void firehose_release(firehose_request_t const **reqs, int numreqs); #endif