| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9862.1 | | SSDEVO::ROLLOW | Dr. File System's Home for Wayward Inodes. | Mon May 19 1997 12:21 | 37 |
| re: amount of virtual memory.
The amount of virtual memory that a process can have is
unrelated to the amount of physical memory in the system.
The kernel has parameters that limit the support virtual
memory size of the system and per-process. With these
raised to suitably large values, only the amount of page
and swap space will limit virtual memory use.
On the V4.0B system I have handy, the address space limit
is 1 GB, with a default data size limit of 128 MB. I was
able to easily raise the datasize limit to the 1 GB mark.
The amount of virtual memory that will be useful and allow
good performance is related to the amount of physical memory.
But if you don't mind the paging, you can easily use virtual
memory in excess of the physical memory if you have enough
page/swap space.
|
| 9862.2 | Virtual Memory | NNTPD::"[email protected]" | Ludmila Mala | Tue May 20 1997 19:31 | 12 |
| This is probably silly question, but how does one check for the address space
limit and the default data size limit?
How do you raise the data size limit?
Are these the values displayed by ulimit -a ( the shell I am using is ksh ) ?
Thanks,
Ludmila
[Posted by WWW Notes gateway]
|
| 9862.3 | | SSDEVO::ROLLOW | Dr. File System's Home for Wayward Inodes. | Wed May 21 1997 02:18 | 7 |
| re: limits.
a. A shell specific command, usually built-in that prints
and controls the limits. I use csh(1), so the built-in
command is simply "limit".
b. The getrusage(2) system call.
|