Sponsored Content
Full Discussion: mmap
Homework and Emergencies Emergency UNIX and Linux Support mmap Post 302567484 by jim mcnamara on Monday 24th of October 2011 10:15:31 AM
Old 10-24-2011
Yes, you can allocate memory in one process and expose it to other processes. It is called shared memory. No, you cannot force another new process to use exclusively the memory you decide to give it.

All of this seems a little odd. You can cause yourself a lot of issues doing something like the above. What are you trying to accomplish, NOT what you think you should to do?
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

mmap

Hello. I'm writing some random access i/o software on Solaris 8 using mmap64 to memory map large files (my test file is ~25 GB). The abbreviated code fragment is: fd = open(cbuf,O_RDONLY|O_LARGEFILE); struct stat statbuf; fstat(fd,&statbuf); off_t len =... (0 Replies)
Discussion started by: gusm
0 Replies

2. HP-UX

mmap failed

We recently have been seeing the following type of error on our development server. Being somewhat new to HP-UX I was hoping to get some insight. Here is what I have found. I have been doing some research. /usr/lib/dld.sl: Call to mmap() failed - TEXT /u07/mdev/lib/libCLEND.sl... (2 Replies)
Discussion started by: scotbuff
2 Replies

3. UNIX for Advanced & Expert Users

mmap and select

I'm using select() to monitor multiple file descriptors (inet sockets) in application. But this application must also collaborate with other applications on the same host via shared memory (mmap'ed file) due to performance reasons. How can I become notification that mmaped memory is changed or... (1 Reply)
Discussion started by: Hitori
1 Replies

4. Solaris

mmap() on 64 bit m/c

Dear Experts, i have a problem related to mmap(), when i run my program on sun for 64 bit which is throwing SIGBUS when it encounters mmap() function, what is the reason how to resolve this one, because it is working for 32 bit. with regards, vidya. (2 Replies)
Discussion started by: vin_pll
2 Replies

5. UNIX for Dummies Questions & Answers

mmap()

how to use mmap() to map a file to memory space. Do you have any simple program???? Because I have to implement lot of concepts into it. (3 Replies)
Discussion started by: gokult
3 Replies

6. Programming

mmap()

how to use mmap() to map a file to memory space. Do you have any simple program???? Because I have to implement lot of concepts into it. (5 Replies)
Discussion started by: gokult
5 Replies

7. Homework & Coursework Questions

mmap

Descriptions: Develop a program that uses mmap() to map a file to memory space. Prepare such a file by yourself and do the follows. <LI class=MsoNormal>Display the content of the file after mapping; <LI class=MsoNormal>Output how many digits included in the file; <LI class=MsoNormal>Replace... (1 Reply)
Discussion started by: gokult
1 Replies

8. Programming

mmap

hai, How do we map 'n' number of files into memory by using mmap system call?? Thanks in advance...... (5 Replies)
Discussion started by: andrew.paul
5 Replies

9. UNIX for Advanced & Expert Users

Regarding MMAP, MLOCK etc..

Hi I want to lock or prevent a portion of memory which I allocated. So I tried MLOCK, MPROTECT and some like this. But all these functions works only on page border. Can I know why that so. Is that possible to protect a portion of memory which is in middle of the page. Example. int A; ... (1 Reply)
Discussion started by: jionnet
1 Replies

10. BSD

Mmap source

I'm new to kernels and C, and I am tinkering around trying to understand OpenBSD's secure memory management. I'm stumped on a couple points. I've read up on malloc() which was apparently modified years ago to allocate memory using mmap. First question, that would be this here, right? ... (4 Replies)
Discussion started by: dcicc
4 Replies
plock(2)							System Calls Manual							  plock(2)

NAME
plock() - lock process, text, data, stack, or shared library in memory SYNOPSIS
DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg- ments to be unlocked. The effective user ID of the calling process must be a user with the privilege. op must be one of the following: Lock text and data segments into memory (process lock) Lock text segment into memory (text lock) Lock data segment into memory (data lock) Remove locks Lock shared library text and shared library data segments (shared library lock) Lock text, data and shared library text and shared library data segments into memory (process and shared library lock) Lock text, shared library text and shared library data segments into memory (text and shared library lock) Lock data, shared library text and shared library data segments into memory (data and shared library lock) Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This practice is not recommended. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
returns the following values: Successful completion. Failure. The requested operation is not performed. is set to indicate the error. ERRORS
If fails, is set to one of the following values. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is equal to and no type of lock exists on the calling process. op is equal to and there are no unlocked shared library segments in the calling process. op is equal to and a process lock, a text lock, or a data lock already exists on the calling process. op is equal to and a text lock or process lock already exists on the calling process. op is equal to and a data lock, or process lock already exists on the calling process. op is not equal to one of the values specified in is not allowed in a window. See vfork(2). There is not enough lockable memory in the system to satisfy the locking request. The effective user ID of the calling process is not a user with the privilege. EXAMPLES
The following call to locks the calling process in memory: SEE ALSO
setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5). STANDARDS CONFORMANCE
plock(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