Messages in this thread | | | Date | Mon, 16 Oct 2000 13:08:29 -0500 (CDT) | From | <> | Subject | Re: large memory support for x86 |
| |
BTW, this fork program did appear to kill about 2 sun servers here... The linux kernel v2.2.16 that they were running survived fine.
On Thu, 12 Oct 2000, Richard B. Johnson wrote:
> On Thu, 12 Oct 2000, Oliver Xymoron wrote: > > > On Wed, 11 Oct 2000, Kiril Vidimce wrote: > > > > > My primary concern is whether a process can allocate more than 4 GB of > > > memory, rather than just be able to use more than 4 GB of physical > > > memory in the system. > > > > Define allocate. There are tricks you can play, but userspace is still a > > flat 32-bit address space per-process. > > > > --- per process. Which means, in principle, that one could have 100 > processes that are accessing a total of 400 Gb of virtual memory. > > It gets to be a bit less than that, though. Process virtual address > space doesn't start at 0 > > Script started on Thu Oct 12 13:25:45 2000 > cat xxx.c > main() > { > printf("main() starts at %p\n", main); > } > # gcc -o xxx xxx.c > # ./xxx > main() starts at 0x8048488 > # exit > exit > Script done on Thu Oct 12 13:26:08 2000 > > > > Cheers, > Dick Johnson > > Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips). > > "Memory is like gasoline. You use it up when you are running. Of > course you get it all back when you reboot..."; Actual explanation > obtained from the Micro$oft help desk. > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |