08-12-2008
ulimit max locked memory virtual memory
Hi,
Would any one be so kind to explain me :
are ulimits defined for each user seperately ? When ?
Specialy what is the impact of :
max locked memory
and
virtual memory
on performance of applications for a user.
Many thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
can anyone explain me what virtual memory is ( for which we use vmstat commande line ) comparing with RAM ?
many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies
2. Programming
Hi,
First of all I appreciate this group very much for its informative discussions and posts.
Here is my question.
I have one process whose virtual memory size increases linearly from 6MB to 12MB in 20 minutes. Does that mean my process has memory leaks?
In what cases does the... (4 Replies)
Discussion started by: shriashishpatil
4 Replies
3. HP-UX
Hi!
I work with HP-UX and I have to monitorize the use of virtual memory for different processes.
(java processes for Tibco Adapter) And if these processes exceed a limit send a message to the syslog.
I donīt know how to monitorize this...
Should I do a script? or use an aplication, for example... (3 Replies)
Discussion started by: Kurohana
3 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
Does anyone know what the best commands in the UNIX command line are for obtaining this info:
current CPU usage
memory usage
virtual memory usage
preferably with date and time parameters too?
thanks
ocelot (4 Replies)
Discussion started by: ocelot
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Can anyone please help me workout how much virtual memory I have running on a T2000 running Solaris 10. Thanks
# df -h
swap 3.5G 1.0M 3.5G 1% /etc/svc/volatile
swap 3.5G 208K 3.5G 1% /tmp
swap 3.5G 56K ... (2 Replies)
Discussion started by: jamba1
2 Replies
6. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
7. Solaris
Hello solaris experts,
Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here.
I understand that, & some questions ....
Locked memory -- memory which will not be swapped out at any cause.
is this for... (0 Replies)
Discussion started by: thegeek
0 Replies
8. Solaris
One of our project has exceeded its assigned max-memory-locked by 3 times .. The said project is using around 9 gigs as described by rss parameter in prstat -J .. and the max-project-memory parameter has been defined as 3gigs .. is it normal or we are monitoring the project memory usage in wrong... (2 Replies)
Discussion started by: fugitive
2 Replies
9. Hardware
Can anyone tell me what the max num of physical memery depends? It's the bit number of the data bus?
How about the max number of the virtual memory? (1 Reply)
Discussion started by: cateran
1 Replies
10. AIX
Hi All,
Anyone know how to capture the nmon avg and max cpu and memory for one of the AIX server for Monthly Utilization Report purposes ?
Thanks.
---------- Post updated at 05:18 AM ---------- Previous update was at 05:07 AM ----------
if possible use shell script to count or sum... (6 Replies)
Discussion started by: ckwan
6 Replies
LEARN ABOUT SUNOS
ddi_umem_unlock
ddi_umem_lock(9F) Kernel Functions for Drivers ddi_umem_lock(9F)
NAME
ddi_umem_lock, ddi_umem_unlock - lock and unlock memory pages
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_umem_lock(caddr_t addr, size_t len, int flags, ddi_umem_cookie_t *cookiep);
void ddi_umem_unlock(ddi_umem_cookie_t cookie);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
PARAMETERS
ddi_umem_lock
addr
Virtual address of memory object
len
Length of memory object in bytes
flags
Valid flags include:
DDI_UMEMLOCK_READ
Memory pages are locked to be read from. (Disk write or a network send.)
DDI_UMEMLOCK_WRITE
Memory pages are locked to be written to. (Disk read or a network receive.)
cookiep
Pointer to a kernel memory cookie.
ddi_umem_unlock
cookie
Kernel memory cookie allocated by ddi_umem_lock().
DESCRIPTION
The ddi_umem_lock(9F) function locks down the physical pages (including I/O pages) that correspond to the current process' virtual address
range [addr, addr + size) and fills in a cookie representing the locked pages. This cookie can be used to create a buf(9S) structure that
can be used to perform I/O (see ddi_umem_iosetup(9F) and ddi_dma_buf_bind_handle(9F)), or it can be used with devmap_umem_setup(9F) to
export the memory to an application.
The virtual address and length specified must be at a page boundary and the mapping performed in terms of the system page size. See page-
size(1).
The flags argument indicates the intended use of the locked memory. Set flags to DDI_UMEMLOCK_READ if the memory pages will be read (for
example, in a disk write or a network send.) Set flags to DDI_UMEMLOCK_WRITE if the memory pages will be written (for example, in a disk
read or a network receive). You must choose one (and only one) of these values.
To unlock the locked pages, the drivers call ddi_umem_unlock(9F) with the cookie obtained from ddi_umem_lock(9F).
The process is not allowed to exec(2) or fork(2) while its physical pages are locked down by the device driver.
The device driver must ensure that the physical pages have been unlocked after the application has called close(2).
RETURN VALUES
On success, a 0 is returned. Otherwise, one of the following errno values is returned.
EFAULT
User process has no mapping at that address range or does not support locking
EACCES
User process does not have the required permission.
ENOMEM
The system does not have sufficient resources to lock memory.
EAGAIN
Could not allocate system resources required to lock the pages. The ddi_umem_lock() could succeed at a later time.
EINVAL
Requested memory is not aligned on a system page boundary.
CONTEXT
The ddi_umem_lock() function can only be called from user context; ddi_umem_unlock() from user, kernel, and interrupt contexts.
SEE ALSO
ddi_umem_iosetup(9F), ddi_dma_buf_bind_handle(9F), devmap_umem_setup(9F), ddi_umem_alloc(9F)
NOTES
The ddi_umem_lock(9F) function consumes physical memory. The driver is responsible for a speedy unlock to free up the resources.
ddi_umem_unlock() can defer unlocking of the pages to a later time depending on the implementation.
SunOS 5.10 4 Feb 2003 ddi_umem_lock(9F)