shared memory synchronisation

10 More Discussions You Might Find Interesting

1. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special...

2. AIX

shared memory

1.How to know wich process is using the shared memory? 2.How to flush (release) the process from the shared memory?

3. UNIX for Advanced & Expert Users

Shared Memory

Hi, Using ipcs we can see shared memory, etc.. details. How can I add/remove shared memory(command name)? Thanks, Naga:cool:

4. Programming

Shared memory for shared library

I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability. Obviously, I'll have to worry about mutual exclusion.

5. Programming

Shared memory in shared library

I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between...

6. Programming

memory sharing - not shared memory -

hi, this is the problem: i want to swap a linked list between 4 processes (unrelated), is there any way i can do that just by sending a pointer to a structure? //example typedef struct node { int x; char c; struct node *next; } node; or i should send the items ( x,c ) by...

7. Programming

help with shared memory

what i want to do is have an int that can been written into by 2 processes but my code doesn't seem to work. #include <sys/types.h> #include <sys/ipc.h> #include <sys/sem.h> #include <sys/shm.h> #include<stdio.h> #define KEY1 (1492) int main() { int shmid; volatile int * addr;...

8. Linux

all about shared memory

Hi all :confused: , I am new to unix.I have been asked to implement shared memory in user's mode.What does this mean?What is the difference it makes in kernel mode and in users mode?What are the advantages of this impemenation(user's mode)? And also i would like to know why exactly shared...

9. UNIX for Advanced & Expert Users

Shared memory shortage but lots of unused memory

I am running HP-UX B.11.11. I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used. But when I try to start the DB with the increased buffer parameter I get told. "Not...

10. Programming

Shared memory

Dear Reader, Is is necessary to attach / dettach the shared memory segments for write operations , if more than one program is accessing same shared memory segments.. I have used semaphore mutex and still I'm getting segmentation fault when I write to the segment when other program is already...

LEARN ABOUT LINUX

sem_init

SEM_INIT(3)						     Linux Programmer's Manual						       SEM_INIT(3)

NAME

       sem_init - initialize an unnamed semaphore

SYNOPSIS

       #include <semaphore.h>

       int sem_init(sem_t *sem, int pshared, unsigned int value);

       Link with -lrt or -pthread.

DESCRIPTION

       sem_init() initializes the unnamed semaphore at the address pointed to by sem.  The value argument specifies the initial value for the sem-
       aphore.

       The pshared argument indicates whether this semaphore is to be shared between the threads of a process, or between processes.

       If pshared has the value 0, then the semaphore is shared between the threads of a process, and should be located at some  address  that	is
       visible to all threads (e.g., a global variable, or a variable allocated dynamically on the heap).

       If pshared is nonzero, then the semaphore is shared between processes, and should be located in a region of shared memory (see shm_open(3),
       mmap(2), and shmget(2)).  (Since a child created by fork(2) inherits its parent's memory mappings, it can also access the semaphore.)   Any
       process that can access the shared memory region can operate on the semaphore using sem_post(3), sem_wait(3), etc.

       Initializing a semaphore that has already been initialized results in undefined behavior.

RETURN VALUE

       sem_init() returns 0 on success; on error, -1 is returned, and errno is set to indicate the error.

ERRORS

       EINVAL value exceeds SEM_VALUE_MAX.

       ENOSYS pshared is nonzero, but the system does not support process-shared semaphores (see sem_overview(7)).

CONFORMING TO

       POSIX.1-2001.

NOTES

       Bizarrely,  POSIX.1-2001  does  not  specify  the value that should be returned by a successful call to sem_init().  POSIX.1-2008 rectifies
       this, specifying the zero return on success.

SEE ALSO

       sem_destroy(3), sem_post(3), sem_wait(3), sem_overview(7)

COLOPHON

       This page is part of release 3.27 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2008-07-27							       SEM_INIT(3)

UNIX for Advanced & Expert Users