Sponsored Content
Full Discussion: all about shared memory
Operating Systems Linux all about shared memory Post 100500 by vijaya2006 on Tuesday 28th of February 2006 03:14:25 AM
Old 02-28-2006
Question all about shared memory

Hi all Smilie ,
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 memory called the fastest IPC mechanism?
 

10 More Discussions You Might Find Interesting

1. 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... (1 Reply)
Discussion started by: joseph_shibu
1 Replies

2. 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... (1 Reply)
Discussion started by: cjcamaro
1 Replies

3. Programming

implement shared memory

hi all I have been asked to implement shared memory in user mode?But :rolleyes: im not understanding how to do this.And what does it mean in user mode?Is it that we need to simulate what kernal does...like attaching ,detaching memory..etc...? And would also like to know why shared memory is... (3 Replies)
Discussion started by: vijaya2006
3 Replies

4. 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;... (6 Replies)
Discussion started by: ddx08
6 Replies

5. 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... (9 Replies)
Discussion started by: elzalem
9 Replies

6. 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... (12 Replies)
Discussion started by: DreamWarrior
12 Replies

7. 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. (0 Replies)
Discussion started by: otheus
0 Replies

8. 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: (2 Replies)
Discussion started by: Nagapandi
2 Replies

9. 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? (1 Reply)
Discussion started by: pchangba
1 Replies

10. 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... (5 Replies)
Discussion started by: iamjag
5 Replies
shm_open(2)							System Calls Manual						       shm_open(2)

NAME
shm_open - create/open a shared memory object SYNOPSIS
DESCRIPTION
The system call establishes a connection between a shared memory object and a file descriptor. It creates an open file description that corresponds to the shared memory object and returns a file descriptor that refers to that open file description. This file descriptor (which is the lowest numbered file descriptor not currently open for that process) is used by other functions to refer to that shared mem- ory object. The name argument points to the shared memory object name, and must conform to the general construction rules for a pathname. The oflag argument is the bitwise inclusive OR of the flags listed under and (these flags are defined in the header file The new file descriptor has the flag set, and consequently does not remain open across system calls. Read-Write Flags The value of oflag must be composed by taking the inclusive OR of exactly one of the following flags: Open for read access only. Open for read and write access. General Flags Any combination of the following flags may also be used in setting the value of oflag. If the shared memory object exists, this flag will have no effect, except as noted under below. Otherwise the shared memory object is created; the shared memory object's user ID is set to the effective user ID of the process; the shared memory object's group ID is set to the effective group ID of the process. The shared memory object's permission bits is set to the value of the mode argument except those set in the file mode creation mask of the process. The new shared memory object will have a size of zero. If and are set in oflag and the named shared memory object exists, will fail. The flag is ignored if is not set in oflag. If the shared memory object exists, and it is successfully opened for reading and writing set in oflag), the object will be truncated to zero length. The mode and owner shall remain unchanged by this function call. RETURN VALUE
returns the following values: n Successful completion. n is the lowest numbered unused file descriptor for the process. Failure. is set to indicate the error. ERRORS
If fails, is set to one of the following values: The shared memory object exists and the permissions specified by oflag are denied, or the shared memory object does not exist and permission to create the it is denied, or is speci- fied and write permission is denied. The and are set in oflag and the named shared memory object already exists. The operation was interrupted by a signal. The operation is not supported for the given name. Too many file descriptors are currently in use by this process. The length of the name string exceeds or the length of a (pathname) component of the name string exceeds while is in effect. Too many shared memory objects are currently open in the system. The flag is not set in oflag and the named shared memory object does not exist. There are insufficient resources for the creation of the new shared memory object. is not supported by the implementation. SEE ALSO
shm_unlink(2), close(2), mmap(2), munmap(2), privileges(5). STANDARDS CONFORMANCE
shm_open(2)
All times are GMT -4. The time now is 06:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy