Messages in this thread | | | From | (H. Peter Anvin) | Subject | Re: 2GB malloc impossible ? | Date | 8 Apr 1999 17:51:07 GMT |
| |
Followup to: <370C8BBC.9BB0C5C3@ccas.ru> By author: "Alexander V. Mirgorodsky" <mirg@ccas.ru> In newsgroup: linux.dev.kernel > > Hi Riley. > > >I would suspect that's the space occupied by the kernel image and > >whatever programs you're running at the time... > > I believe 700Mb is too much for kernel image, etc.: I can run two > processes simultaneously each one malloc'ing and intensively memset'ing > its own (1GB - eps) without Any swapping. > > BTW 700Mb looks like a hardcoded constant - it is always the same > (0x2aaab000) with the only exception: systems with 3:1 split prefer to > start allocation at smth like 0x4000b000. >
I bet it is the end of libc.
-hpa -- "The user's computer downloads the ActiveX code and simulates a 'Blue Screen' crash, a generally benign event most users are familiar with and that would not necessarily arouse suspicions." -- Security exploit description on http://www.zks.net/p3/how.asp
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |