Sponsored Content
Top Forums UNIX for Beginners Questions & Answers 32 bit process addressing more than 4GB Post 303042481 by Neo on Thursday 26th of December 2019 09:33:40 PM
Old 12-26-2019
A 32-bit system generally cannot physically address more than 4GB of RAM.

Various systems, however, have adopted extensions that permit a 32-bit system to physically access more than 4GB of RAM.

In generally, this is implemented via "page table hacks".

For example, the x86 architecture, for example, supports a feature called Physical Address Extension (PAE) that commonly extends physically-addressable memory to 64GB.

PAE is quite common. If your system supports it, you can have more than 4GB of RAM. Otherwise you are stuck at 4GB.

You might check to see if your SPARC architecture also supports PAE and post back the results of your research.
 

6 More Discussions You Might Find Interesting

1. Programming

copying or concatinating string from 1st bit, leaving 0th bit

Hello, If i have 2 strings str1 and str2, i would like to copy/concatenate str2 to str1, from 1st bit leaving the 0th bit. How do i do it? (2 Replies)
Discussion started by: jazz
2 Replies

2. AIX

fiber with 4GB

Hi, It's my first time I will use a 4BG fiber with two ports on one card. I used only one port 2GB before. What will be the drivers I need to install on my AIX5.3? Is the two ports going to be just one line? Or I can use the other ports on another connection. Thanks in advance, itik (1 Reply)
Discussion started by: itik
1 Replies

3. Homework & Coursework Questions

Four-Level multi-paging on x86 system with 64 bit addressing

1. The problem statement, all variables and given/known data: Hi all, I've got a huuuuuuge problem with understanding this new concept of multi-paging. I really tried to research but i could not find anything significant. I've been trying to understand this for 4 days and i cannot. The question... (0 Replies)
Discussion started by: snowboarder
0 Replies

4. Red Hat

process fails if setuid bit is set

Hi, OS : Linux I have an executable (P1) owned by user say "abcd" and the setuid bit is set. And there is another executable (P2) which brings up the process (P1). When the setuid bit is set, the process P1 is failing, if the setuid bit is not set there is no issue. I was wondering if... (6 Replies)
Discussion started by: ahamed101
6 Replies

5. Shell Programming and Scripting

How to handle 64 bit arithmetic operation at 32 bit compiled perl interpreter?H

Hi, Here is the issue. From the program snippet I have Base: 0x1800000000, Size: 0x3FFE7FFFFFFFF which are of 40 and 56 bits. SO I used use bignum to do the math but summing them up I always failed having correct result. perl interpreter info, perl, v5.8.8 built for... (0 Replies)
Discussion started by: rrd1986
0 Replies

6. Windows & DOS: Issues & Discussions

Which version of Windows Vista to install with a product key? 32-bit or 64-bit?

Hello everyone. I bought a dell laptop (XPS M1330) online which came without a hard drive. There is a Windows Vista Ultimate OEMAct sticker with product key at the bottom case. I checked dell website (here) for this model and it says this model supports both 32 and 64-bit version of Windows... (4 Replies)
Discussion started by: milhan
4 Replies
services.window(4)					     Kernel Interfaces Manual						services.window(4)

NAME
services.window - file containing applications and their associated memory window ID DESCRIPTION
The file is used by applications using memory windows. Each line in the file associates an application with a memory window ID. A line in the file cannot start with a space or tab. The format is a unique name, defining the application, followed by a space/tab, followed by a unique window_id. See the sample file in Memory windows allows for the starting of a process in a unique or existing memory window where it can create and share objects with other applications in the same memory window. The creation of memory windows removes the system wide restriction on shared resources. Without memory windows, 32-bit processes were lim- ited to 1.75 gigabytes of shared resources. Each memory window allows for the definition of a unique 1 gigabyte quadrant and since multi- ple memory windows can be defined in a system, the system total for shared resources can exceed the 1.75 gigabyte limitation for 32 bit processes. The definition of a memory window is only available for 32-bit processes. The file provides a central place for memory window applications to associate their memory window IDs. In the event there are any colli- sions, only a change in is necessary to select another memory window for the entire application. If is not used, and user applications hard code window IDs in their startup scripts, collisions are not easily detected or easily fixed. A memory window application uses the command getmemwindow(1M) to extract the application's window_id from the file, and then passes that ID to the setmemwindow(1M). Using the same window ID places applications in the same memory window. EXAMPLES
Below is a example of a file. AUTHOR
was developed by HP. FILES
File containing applications' associated window ID. SEE ALSO
getmemwindow(1M), setmemwindow(1M). on services.window(4)
All times are GMT -4. The time now is 06:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy