Simple multitasking communication

7 posts / 0 new

Last post

Wed, 2015-09-16 04:47

mritter0

Offline

Last seen: 3 years 1 month ago

Joined: 2014-04-21 21:15

Simple multitasking communication

I am trying to write a simple multitasking communication function. Not quite there.

My program starts. SetUpProcesses() to start new process. I can't talk to it. I never get past IExec->WaitPort(). (The process is started.)

I just want to PutMsg() a simple message with a int32 value to tell it what to do, 1 through 99. -1 to quit. Or even send a text message, "start", "stop", "quit". A reply back that it's done would be nice, success or fail.

I based this off Thomas Rapp's multi3.c example. Tried to update it to OS4.

Can someone straighten me out?

from Protos.h:
extern struct MyMessage
{
	struct Message			Msg;		// need this????
 
	int32					ActionID;
 
	int32					ResultID;
} *MyMsg;
 
 
struct MyMessage			*MyMsg;
struct MsgPort				*SetMenuStatePort=NULL;
struct Process				*SetMenuStateProcess=NULL;
 
 
BOOL
SetUpProcesses()
{
	if (!(ReplyPort=(struct MsgPort *)IExec->AllocSysObject(ASOT_PORT,NULL)))
		return(FALSE);
 
// Probably don't need this
	if ((MyMsg=IExec->AllocSysObjectTags(ASOT_MESSAGE,
		ASOMSG_Size,				sizeof(struct MyMessage),
		ASOMSG_ReplyPort,			ReplyPort,
	TAG_END)))
	{
		return(FALSE);
	}
 
	if (!(SetMenuStatePort=(struct MsgPort *)IExec->AllocSysObject(ASOT_PORT,NULL)))
		return(FALSE);
	else
	{
		SetMenuStateSig=PORTMASK(SetMenuStatePort);
 
		if ((SetMenuStateProcess=IDOS->CreateNewProcTags(
			NP_Entry, NP_SetMenuStateProcess,
//			NP_NotifyOnDeathSigTask, me, /* SIGB_CHILD signal */
 
//			NP_FinalCode, finalfunc, /* executes this ending */
//			NP_FinalData, fd,      /* tracking data for above */
 
//			NP_EntryCode, entryfunc, /* executes this starting */
//			NP_EntryData, fd,      /* tracking data for above */
 
			NP_Child, TRUE,
			NP_ExitData, IDOS, /* share idos with children. */
		TAG_DONE)))
		{
			IDOS->Printf("Started SetMenuStateProcess\n");
		}
		else
			return(FALSE);
	}
 
	return(TRUE);
}
 
 
BOOL
SendCommandToPort(struct MsgPort *replyport,struct MsgPort *cmdport,int32 ActionID)
{
	struct MyMessage		*MyMsg;
 
	if ((MyMsg=IExec->AllocSysObjectTags(ASOT_MESSAGE,
		ASOMSG_Size,				sizeof(struct MyMessage),
		ASOMSG_ReplyPort,			replyport,
	TAG_END)))
	{
		MyMsg->Msg.mn_ReplyPort=replyport;
		MyMsg->ActionID=ActionID;
 
		IExec->PutMsg(cmdport,(struct Message *)MyMsg);
	}
 
// free the message???
 
	return(TRUE);
}
 
 
int32
GetPortResponse(struct MsgPort *replyport)
{
	struct MyMessage		*MyMsg;
	int32					Result=-1;
 
	if ((MyMsg=(struct MyMessage *)IExec->GetMsg(replyport)))
	{
		Result=MyMsg->ResultID;
		IExec->FreeSysObject(ASOT_MESSAGE,MyMsg);	// how does it know the pointer???
	}
 
	return(Result);
}
 
 
VOID
ShutDownProcesses()
{
	if (SetMenuStateProcess)
	{
		if (SendCommandToPort(ReplyPort,SetMenuStatePort,-1))
		{
			IExec->WaitPort(ReplyPort);
			GetPortResponse(ReplyPort);
		}
	}
 
	if (SetMenuStatePort)
		IExec->FreeSysObject(ASOT_PORT,SetMenuStatePort);
 
	if (MyMsg)
		IExec->FreeSysObject(ASOT_MESSAGE,MyMsg);
 
	if (ReplyPort)
		IExec->FreeSysObject(ASOT_PORT,ReplyPort);
}
 
 
//////////////////////////////
 
 
int32
NP_SetMenuStateProcess(STRPTR *args UNUSED,int32 arglen UNUSED,struct ExecBase *sysbase)
{
//	struct ExecIFace		*iexec=(APTR)sysbase->MainInterface;
//	struct Process			*me=(APTR)iexec->FindTask(0);
//	struct DOSIFace			*idos=(APTR)me->pr_ExitData; /* via parent */
	uint32					Loc=AT_NOWHERE;
	int32					Action;
	BOOL					done=FALSE;
	struct MyMessage		*MyMsg;
 
//	if ((MyMsg=IExec->AllocSysObjectTags(ASOT_MESSAGE,
//		ASOMSG_Size,				sizeof(struct MyMessage),
//		ASOMSG_ReplyPort,			replyport,
//	TAG_END)))
	{
		while(!done)
		{
			IExec->WaitPort(SetMenuStatePort);
			while((MyMsg=(struct MyMessage *)IExec->GetMsg(SetMenuStatePort)))
			{
				Action=MyMsg->ActionID;
				IExec->ReplyMsg(&MyMsg->Msg);
				switch(Action)
				{
					case 1:
						if (Loc != SMSLocation)
						{
							IIntuition->DisplayBeep(NULL);	// just visual to know worked
							Loc=SMSLocation;
						}
						break;
 
					case 2:
						// do something else
						break;
 
					case -1:
						done=TRUE;
						break;
				}
			}
		}
 
//		IExec->FreeSysObject(ASOT_MESSAGE,MyMsg);
	}
 
	return(RETURN_OK);
}

Wed, 2015-09-16 14:22

broadblues

Offline

Last seen: 5 years 5 months ago

Joined: 2012-05-02 21:48

Re: Simple multitasking communication

Not 100% sure by shouldn't you be allocating the SetMenuState port on it's own process? A port has a signal bit set etc and signal masks are per Process.

I not sure what your end goal is but I wondering why menu updating needs to be asynchronous? Perhaps you are doing more than that.

If you want to send textual commands you might consider using arexx.class would cut out a lot of work, though again it depends on your end goal.

[edit]
Why are you passing IDOS as NP_ExitData?

[moreedit]

You shoul do all your setup on the new process itself. Ie Allocate the Port etc.

After starting the process, the parent should wait on a signal SIGBREAKF_CTRL_F is a good or at least common choice, and the child should signal the parent when setup is done and it's safe to continue.

Wed, 2015-09-16 19:03

mritter0

Offline

Last seen: 3 years 1 month ago

Joined: 2014-04-21 21:15

Re: Simple multitasking communication

I had a hunch about where to create the ports. Will try it in the new process.

Passing IDOS in np_ExitData is from one of the AutoDocs examples.

This is my first attempt at this. Simple little thing to test and get working.

Thanks

Fri, 2015-09-18 05:26

mritter0

Offline

Last seen: 3 years 1 month ago

Joined: 2014-04-21 21:15

Re: Simple multitasking communication

Got it working. Create the port in the new process was key. Thanks

Mon, 2015-09-21 05:12

mritter0

Offline

Last seen: 3 years 1 month ago

Joined: 2014-04-21 21:15

Re: Simple multitasking communication

So I have my IDOS->CreateNewProcTags() process up and running. To truly be multitasking should ALL the processing be done in the new process? Or can it call external functions and not affect the main program? I am calling an external function and it seems to work fine. But it is simple and may not notice and "slow down" of the main program.

Mon, 2015-09-21 14:56

(Reply to #5) #6

thomas

Offline

Last seen: 1 month 1 week ago

Joined: 2011-05-16 14:23

Re: Simple multitasking communication

Tasks created by CreateNewProc are completely independent. If you call a subroutine your main routine might call, too, then this subroutine must be reentrant, i.e. it must be able to run twice at the same time. If you need serialized access to resources, you have to use SignalSemaphores. There is no automatic serialization taking place. This is especially important if you share linked lists (struct List, struct Node) or similar. These things are not protected at all, you have to protect them manually.

Wed, 2015-09-23 19:13

(Reply to #6) #7

salass00

Offline

Last seen: 1 month 2 weeks ago

Joined: 2011-02-03 11:27

Re: Simple multitasking communication

Passing IDOS in np_ExitData is from one of the AutoDocs examples.

NP_ExitData is meant for passing data to be used by the NP_ExitCode function.

Using it for anything else is not something I would recommend ever doing. If you need to pass data to a child process without using global variables either use NP_UserData or send a startup message to the process' pr_MsgPort that the process then waits for and gets before doing anything else.

Search form

User login