04-28-2012
32-bit x86 has hardware limitations of 64 gigabytes. You're using a 64-bit processor with a 32-bit kernel why?
9 More Discussions You Might Find Interesting
1. Programming
Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10.
My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies
2. HP-UX
Refer from title:
How can i get memory used or anything that can show memory from sar file
example on solaris:-
we can use sar with option to show memory used at time that sar crontab run.
on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies
3. AIX
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.
PS :
this is what I can see in MAN :
ulimit ]
... (5 Replies)
Discussion started by: big123456
5 Replies
4. 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
5. Programming
Hi,
I'm trying to learn how to manage memory when I have to deal with lots of data.
Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that
holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at
once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 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
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
9. SCO
Sir I have installed unixware7.1.3 on vmware workstation previously and I have allotted 8GB to the whole system.
I want to add extra space to the existing system by using another virtual harddisk added by using VMware.
Kindly suggest the procedure.
Regards,
Rupesh. (3 Replies)
Discussion started by: rupeshforu3
3 Replies
VIOMB(4) BSD Kernel Interfaces Manual VIOMB(4)
NAME
viomb -- VirtIO memory ballooning driver
SYNOPSIS
virtio* at pci? dev ? function ?
viomb* at virtio?
DESCRIPTION
virtio(4) defines an interface for efficient, standard, and extensible I/O between the hypervisor and the virtual machine. The viomb driver
supports the virtio-compliant memory ballooning device.
Memory ballooning works as follows:
1. The host operator requests a guest to return some amount of memory to the host (via e.g. Qemu monitor balloon command).
2. The hypervisor sends the request via VirtIO memory ballooning device.
3. The guest viomb driver requests allocation of that amount of physical memory from the NetBSD memory management system.
4. The viomb device tells the hypervisor the guest physical memory address of the allocated memory via VirtIO memory ballooning device.
The sysctl node hw.viomb.npages shows the requested number of memory pages to return to the hypervisor, while hw.viomb.actual shows the
actual number of memory pages that are already returned to the hypervisor.
SEE ALSO
virtio(4), sysctl(8)
Rusty Russell, IBM Corporation, Virtio PCI Card Specification, http://ozlabs.org/~rusty/virtio-spec/.
HISTORY
The viomb device driver appeared in NetBSD 6.0.
BUGS
The userland interface should be same as the Xen ballooning device.
BSD
November 26, 2011 BSD