08-21-2003
physical memory
It is just a general question....is there a limit on the memory? I am looking into a process to store image files on the unix server which will be accessed by the application, and I just wonder if there is any limit regarding the physical or virtual memory. I am very new to unix, so thanks for any help!
10 More Discussions You Might Find Interesting
1. Programming
Hi,
My problem is next....
How can I work with physical memory in the Unix FreeBSD 2.2 or hight?
What is the "mem" & "kmem" drivers?
P.S./ writing device driver for UNIX FreeBSD 2.2 :D (2 Replies)
Discussion started by: Alex_T
2 Replies
2. Shell Programming and Scripting
What command can i use to get the physical and virtual memory of a database? (7 Replies)
Discussion started by: tads98
7 Replies
3. UNIX for Advanced & Expert Users
vmstat -P commands gives me an output as shown at the end of this message.
my first question is about the difference between "total physical memory" and "total physical memory use"
"Total Physical Memory" -"Total Physical Memory Use"
524288 pages-524026 pages= 262 pages
does it mean... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies
4. Solaris
HI
Please help me how to check the physical memory, model name and hardisk information. (5 Replies)
Discussion started by: jeelans
5 Replies
5. Solaris
what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ? (2 Replies)
Discussion started by: jayaramanit
2 Replies
6. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
7. 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
8. AIX
IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Discussion started by: 1computerman
2 Replies
9. UNIX for Dummies Questions & Answers
I am currently running unix open server 6.0 on a Dell Power Edge R720. The system will be running fine when the blue screen appears and states the system has performed a physical memory dump in # of ticks. I reboot the system and all looks well. Running diagnostics does not show anything wrong. The... (1 Reply)
Discussion started by: rformt
1 Replies
10. Solaris
Below is Physical Memory result :
-bash-3.00$ prtconf | grep "Memory size"
Memory size: 36854 Megabytes
-bash-3.00$ vmstat 1 2 | tail -1
0 0 0 28220616 1318888 15 143 0 0 0 0 0 253 2 15 0 5215 14989 5917 7 0 93
and the script i have to calculate this in Percentage is :
#!/bin/sh... (3 Replies)
Discussion started by: mjoshi010207
3 Replies
MEM(4) Kernel Interfaces Manual MEM(4)
NAME
mem, kmem - main memory
SYNOPSIS
major device number(s):
raw: 1
minor device encoding:
mem: 0; kmem: 1; null: 2
DESCRIPTION
Mem is a special file that is an image of the main memory of the computer. It may be used, for example, to examine (and even to patch) the
system.
Byte addresses in mem are interpreted as physical memory addresses. References to non-existent locations cause errors to be returned.
The file kmem is the same as mem except that kernel virtual memory rather than physical memory is accessed. Only kernel virtual addresses
that are mapped to memory are allowed. Examining and patching device registers is likely to lead to unexpected results when read-only or
write-only bits are present.
On PDP-11s, the I/O page begins at location 0160000 of kmem and the per-process data segment for the current process begins at 0140000 and
is USIZE clicks (64 bytes each) long.
FILES
/dev/mem
/dev/kmem
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
BUGS
On PDP-11's, specifying an odd kernel or user address, or an odd transfer count is [generally] slower than using all even parameters.
On machines with ENABLE/34(tm) memory mapping boards the I/O page can be accessed only through kmem.
3rd Berkeley Distribution January 28, 1988 MEM(4)