5

This program works (I tested it), even though the semaphore is not in shared memory. Note how I create the variable once - before the fork().

On the other hand, a semaphore created with sem_init() needs to be in shared memory to work. But it's still a sem_t structure, so why doesn't it require shared memory?

Are the contents of the sem_t structure somehow different?

sem_t *s = sem_open("mysemaphore1", O_CREAT, 0600, 0);
if (fork()) {
    sleep(3);
    sem_post(s);
} else {
    sem_wait(s);
    printf("Woke\n");
}
sashoalm
  • 75,001
  • 122
  • 434
  • 781

1 Answers1

8

The semaphore created by sem_open() is a named semaphore. The basic purpose of named semaphore is to be used between unrelated processes. The semaphore created by sem_init() is an unnamed semaphore. It is light weight than the named semaphore and needs to be put in shared memory if used between related processes. If used between threads of the same process, it can be kept in global variable.

The pointer returned by the sem_open() is actually a pointer to a memory mapped by mmap() with MAP_SHARED flag set. Since such kind of memory persists across fork(), hence you are able to use the same variable in both parent and child to access the named semaphore.

martineau
  • 119,623
  • 25
  • 170
  • 301
Vikram Singh
  • 948
  • 6
  • 10
  • 1
    But why is using the same variable working - note I use the same variable in both the forked processes, instead of making a separate call to `sem_open()` for each one. – sashoalm Jan 15 '14 at 07:52
  • 3
    Because the variable in question is a pointer that has been set by `sem_open` before the fork. The pointer, its contents (i.e. the address of the semaphore), and the shared memory contents (the semaphore) it points to are inherited across the `fork`. – Duck Jan 16 '14 at 13:44