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
bcopy(9F) Kernel Functions for Drivers bcopy(9F)
NAME
bcopy - copy data between address locations in the kernel
SYNOPSIS
#include <sys/types.h>
#include <sys/sunddi.h>
void bcopy(const void *from, void *to, size_t bcount);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI).
PARAMETERS
from Source address from which the copy is made.
to Destination address to which copy is made.
bcount The number of bytes moved.
DESCRIPTION
bcopy() copies bcount bytes from one kernel address to another. If the input and output addresses overlap, the command executes, but the
results may not be as expected.
Note that bcopy() should never be used to move data in or out of a user buffer, because it has no provision for handling page faults. The
user address space can be swapped out at any time, and bcopy() always assumes that there will be no paging faults. If bcopy() attempts to
access the user buffer when it is swapped out, the system will panic. It is safe to use bcopy() to move data within kernel space, since
kernel space is never swapped out.
CONTEXT
bcopy() can be called from user or interrupt context.
EXAMPLES
Example 1: Copying data between address locations in the kernel:
An I/O request is made for data stored in a RAM disk. If the I/O operation is a read request, the data is copied from the RAM disk to a
buffer (line 8). If it is a write request, the data is copied from a buffer to the RAM disk (line 15). bcopy() is used since both the RAM
disk and the buffer are part of the kernel address space.
1 #define RAMDNBLK 1000 /* blocks in the RAM disk */
2 #define RAMDBSIZ 512 /* bytes per block */
3 char ramdblks[RAMDNBLK][RAMDBSIZ]; /* blocks forming RAM
/* disk
...
4
5 if (bp->b_flags & B_READ) /* if read request, copy data */
6 /* from RAM disk data block */
7 /* to system buffer */
8 bcopy(&ramdblks[bp->b_blkno][0], bp->b_un.b_addr,
9 bp->b_bcount);
10
11 else /* else write request, */
12 /* copy data from a */
13 /* system buffer to RAM disk */
14 /* data block */
15 bcopy(bp->b_un.b_addr, &ramdblks[bp->b_blkno][0],
16 bp->b_bcount);
SEE ALSO
copyin(9F), copyout(9F)
Writing Device Drivers
WARNINGS
The from and to addresses must be within the kernel space. No range checking is done. If an address outside of the kernel space is
selected, the driver may corrupt the system in an unpredictable way.
SunOS 5.10 4 August 2003 bcopy(9F)