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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
arch_prctl
ARCH_PRCTL(2) Linux Programmer's Manual ARCH_PRCTL(2)
NAME
arch_prctl - set architecture-specific thread state
SYNOPSIS
#include <asm/prctl.h>
#include <sys/prctl.h>
int arch_prctl(int code, unsigned long addr);
int arch_prctl(int code, unsigned long *addr);
DESCRIPTION
The arch_prctl() function sets architecture-specific process or thread state. code selects a subfunction and passes argument addr to it;
addr is interpreted as either an unsigned long for the "set" operations, or as an unsigned long *, for the "get" operations.
Sub functions for x86-64 are:
ARCH_SET_FS
Set the 64-bit base for the FS register to addr.
ARCH_GET_FS
Return the 64-bit base value for the FS register of the current thread in the unsigned long pointed to by addr.
ARCH_SET_GS
Set the 64-bit base for the GS register to addr.
ARCH_GET_GS
Return the 64-bit base value for the GS register of the current thread in the unsigned long pointed to by addr.
RETURN VALUE
On success, arch_prctl() returns 0; on error, -1 is returned, and errno is set to indicate the error.
ERRORS
EFAULT addr points to an unmapped address or is outside the process address space.
EINVAL code is not a valid subcommand.
EPERM addr is outside the process address space.
CONFORMING TO
arch_prctl() is a Linux/x86-64 extension and should not be used in programs intended to be portable.
NOTES
arch_prctl() is only supported on Linux/x86-64 for 64-bit programs currently.
The 64-bit base changes when a new 32-bit segment selector is loaded.
ARCH_SET_GS is disabled in some kernels.
Context switches for 64-bit segment bases are rather expensive. It may be a faster alternative to set a 32-bit base using a segment selec-
tor by setting up an LDT with modify_ldt(2) or using the set_thread_area(2) system call in kernel 2.5 or later. arch_prctl() is only
needed when you want to set bases that are larger than 4GB. Memory in the first 2GB of address space can be allocated by using mmap(2)
with the MAP_32BIT flag.
As of version 2.7, glibc provides no prototype for arch_prctl(). You have to declare it yourself for now. This may be fixed in future
glibc versions.
FS may be already used by the threading library.
SEE ALSO
mmap(2), modify_ldt(2), prctl(2), set_thread_area(2)
AMD X86-64 Programmer's manual
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2007-12-26 ARCH_PRCTL(2)