VMS/VMS_Implementations/VSs_impls/VSs__MC_shared

comparison VSs.c @ 4:13af59ed7ea5

Works -- with send-receive plus normal dependencies

author	Sean Halle <seanhalle@yahoo.com>
date	Thu, 14 Jun 2012 18:44:47 -0700
parents	468b8638ff92
children	8188c5b4bfd7

comparison

equal deleted inserted replaced

-:f98d42cee3ff
+:b7ea637e1c74
 semanticEnv->nextCoreToGetNewSlv = 0;
 semanticEnv->numSlaveVP = 0;
 semanticEnv->argPtrHashTbl  = makeHashTable32( 16, &VMS_int__free );
+semanticEnv->commHashTbl    = makeHashTable32( 16, &VMS_int__free );
 //TODO: bug -- turn these arrays into dyn arrays to eliminate limit
 //semanticEnv->singletonHasBeenExecutedFlags = makeDynArrayInfo( );
 //semanticEnv->transactionStrucs = makeDynArrayInfo( );
 for( i = 0; i < NUM_STRUCS_IN_SEM_ENV; i++ )
 //===========================================================================
-//===========================================================================
+//======================= task submit and end ==============================
-/*Returns a taskID, which can be used to communicate between tasks with
+/*
-* send-receive, or to use other kinds of constructs with tasks.
+*/
-*/
+void
-int32
 VSs__submit_task( VSsTaskType *taskType, void *args, SlaveVP *animSlv)
 { VSsSemReq  reqData;
 reqData.reqType    = submit_task;
-reqData.callingSlv = animSlv;
 reqData.taskType   = taskType;
 reqData.args       = args;
+reqData.callingSlv = animSlv;
+reqData.taskID     = NULL;
 VMS_WL__send_sem_request( &reqData, animSlv );
-return (int32)animSlv->dataRetFromReq;
+}
-}
+inline int32 *
-/*NOTE: if want, don't need to send the animating SlaveVP around..
+VSs__create_taskID_of_size( int32 numInts, SlaveVP *animSlv )
-* instead, can make a single slave per core, and coreCtrlr looks up the
+{ int32 *taskID;
-* slave from having the core number.
-*
+taskID    = VMS_WL__malloc( sizeof(int32) + numInts * sizeof(int32) );
-*But, to stay compatible with all the other VMS languages, leave it in..
+taskID[0] = numInts;
-*
+return taskID;
-*This call is the last to happen in every task.  It causes the slave to
+}
+void
+VSs__submit_task_with_ID( VSsTaskType *taskType, void *args, int32 *taskID,
+SlaveVP     *animSlv)
+{ VSsSemReq  reqData;
+reqData.reqType    = submit_task;
+reqData.taskType   = taskType;
+reqData.args       = args;
+reqData.taskID     = taskID;
+reqData.callingSlv = animSlv;
+VMS_WL__send_sem_request( &reqData, animSlv );
+}
+/*This call is the last to happen in every task.  It causes the slave to
 * suspend and get the next task out of the task-queue.  Notice there is no
 * assigner here.. only one slave, no slave ReadyQ, and so on..
 *Can either make the assigner take the next task out of the taskQ, or can
 * leave all as it is, and make task-end take the next task.
 *Note: this fits the case in the new VMS for no-context tasks, so will use
 * the built-in taskQ of new VMS, and should be local and much faster.
 *
 *The task-stub is saved in the animSlv, so the request handler will get it
 * from there, along with the task-type which has arg types, and so on..
+*
+* NOTE: if want, don't need to send the animating SlaveVP around..
+* instead, can make a single slave per core, and coreCtrlr looks up the
+* slave from having the core number.
+*
+*But, to stay compatible with all the other VMS languages, leave it in..
 */
 void
 VSs__end_task( SlaveVP *animSlv )
 { VSsSemReq  reqData;
 reqData.reqType      = end_task;
 reqData.callingSlv   = animSlv;
 VMS_WL__send_sem_request( &reqData, animSlv );
 }
+//==========================  send and receive ============================
+//
+inline int32 *
+VSs__give_self_taskID( SlaveVP *animSlv )
+{
+return ((VSsSemData*)animSlv->semanticData)->taskStub->taskID;
+}
+//================================ send ===================================
+void
+VSs__send_of_type_to( void *msg, const int32 type, int32 *receiverID,
+SlaveVP *senderSlv )
+{ VSsSemReq  reqData;
+reqData.reqType    = send_type_to;
+reqData.msg        = msg;
+reqData.msgType    = type;
+reqData.receiverID = receiverID;
+reqData.senderSlv  = senderSlv;
+reqData.nextReqInHashEntry = NULL;
+VMS_WL__send_sem_request( &reqData, senderSlv );
+//When come back from suspend, no longer own data reachable from msg
+}
+void
+VSs__send_from_to( void *msg, int32 *senderID, int32 *receiverID, SlaveVP *senderSlv )
+{ VSsSemReq  reqData;
+reqData.reqType     = send_from_to;
+reqData.msg         = msg;
+reqData.senderID    = senderID;
+reqData.receiverID  = receiverID;
+reqData.senderSlv   = senderSlv;
+reqData.nextReqInHashEntry = NULL;
+VMS_WL__send_sem_request( &reqData, senderSlv );
+}
+//================================ receive ================================
+/*The "type" version of send and receive creates a many-to-one relationship.
+* The sender is anonymous, and many sends can stack up, waiting to be
+* received.  The same receiver can also have send from-to's
+* waiting for it, and those will be kept separate from the "type"
+* messages.
+*/
+void *
+VSs__receive_type_to( const int32 type, int32* receiverID, SlaveVP *receiverSlv )
+{       DEBUG__printf1(dbgRqstHdlr,"WL: receive type to %d",receiverID[1] );
+VSsSemReq  reqData;
+reqData.reqType     = receive_type_to;
+reqData.msgType     = type;
+reqData.receiverID  = receiverID;
+reqData.receiverSlv = receiverSlv;
+reqData.nextReqInHashEntry = NULL;
+VMS_WL__send_sem_request( &reqData, receiverSlv );
+return receiverSlv->dataRetFromReq;
+}
+/*Call this at the point a receiving task wants in-coming data.
+* Use this from-to form when know senderID -- it makes a direct channel
+* between sender and receiver.
+*/
+void *
+VSs__receive_from_to( int32 *senderID, int32 *receiverID, SlaveVP *receiverSlv )
+{
+VSsSemReq  reqData;
+reqData.reqType     = receive_from_to;
+reqData.senderID    = senderID;
+reqData.receiverID  = receiverID;
+reqData.receiverSlv = receiverSlv;
+reqData.nextReqInHashEntry = NULL;
+DEBUG__printf2(dbgRqstHdlr,"WL: receive from %d to: %d", reqData.senderID[1], reqData.receiverID[1]);
+VMS_WL__send_sem_request( &reqData, receiverSlv );
+return receiverSlv->dataRetFromReq;
+}
 //==========================================================================
 //
 /*A function singleton is a function whose body executes exactly once, on a
 * single core, no matter how many times the fuction is called and no

Mercurial > cgi-bin > hgwebdir.cgi > VMS > VMS_Implementations > VSs_impls > VSs__MC_shared_impl

comparison VSs.c @ 4:13af59ed7ea5