views:

1413

answers:

3

hi,

can someone help me about how to create multiple child processes which have the same parent in order to do "some" part of particular job?

for example, an external sorting algorithm which is applied with child processes; each child process sorts a part of data and finally the parent merges them..

EDIT: Maybe I should mention the forking multiple child processes with loop..

A: 

You can do this with fork. A given parent can fork as may times as it wants. However, I agree with AviD pthreads may be more appropriate.

pid_t firstChild, secondChild;
firstChild = fork();
if(firstChild != 0)
{
  // In parent
  secondChild = fork();
  if(secondChild != 0)
  {
    // In parent
  }
  else
  {
    // In secondChild
  }
}
else
{
  // In firstChild
}
Matthew Flaschen
+1  A: 

Here is how to fork 10 children and wait for them to finish:

pid_t pids[10];
int i;
int n = 10;

/* Start children. */
for (i = 0; i < n; ++i) {
  if ((pids[i] = fork()) < 0) {
    perror("fork");
    abort();
  } else if (pids[i] == 0) {
    DoWorkInChild();
    exit(0);
  }
}

/* Wait for children to exit. */
int status;
pid_t pid;
while (n > 0) {
  pid = wait(&status);
  printf("Child with PID %ld exited with status 0x%x.\n", (long)pid, status);
  --n;  // TODO(pts): Remove pid from the pids array.
}
pts
i didn't really get the second part(wait for children to exit).. what does status mean? is that a child process property?
israkir
Status is the exit status of the child process. It depends on the exit(...) value, or if the process is killed by a signal, then it depends on the signal number. See this for more: http://linux.die.net/man/2/wait
pts
+2  A: 

I think it would be worth pointing out why threads are more appropriate here:

As you are trying to do a "part" of the job in parallel i assume that your program needs to know about the result of the computation. fork()s of a process don't share more then the initial information after fork(). Every change in one process is unknow to the other and you would need to pass the information as a message (e.g. through a pipe, see "man pipe"). Threads in a process share the same adress space and therefor are able to manipulate data and have them visible toeach other "immediatly". Also adding the benefits of being more lightweight, I'd go with pthreads().

After all: You will learn all you need to know about fork() if you use pthreads anyway.

pmr