Messages in this thread | | | From | (david parsons) | Subject | Re: Reserved memory | Date | 7 Feb 2000 19:34:18 -0800 |
| |
In article <linux.kernel.389BEEDF.5CCCB33@grad.physics.sunysb.edu>, Rui Sousa <rsousa@grad.physics.sunysb.edu> wrote: >Hi, > >Can someone explain me what is happening here? > >kernel 2.2.14 SMP: > >Jan 25 01:03:45 localhost kernel: >Memory: 128392k/131072k available (692k kernel code, 424k reserved, 1516k data, >48k init) > >kernel 2.3.42 SMP: > >Feb 3 18:48:29 localhost kernel: e820: 0009fc00 @ 00000000 (usable) >Feb 3 18:48:29 localhost kernel: e820: 00000400 @ 0009fc00 (reserved) >Feb 3 18:48:29 localhost kernel: e820: 00020000 @ 000e0000 (reserved) >Feb 3 18:48:29 localhost kernel: e820: 07f00000 @ 00100000 (usable) >Feb 3 18:48:29 localhost kernel: e820: 00001000 @ fec00000 (reserved) >Feb 3 18:48:29 localhost kernel: e820: 00001000 @ fee00000 (reserved) >Feb 3 18:48:29 localhost kernel: e820: 00040000 @ fffc0000 (reserved)
This reserved memory is memory that's reserved by the bios; it's either rom (009fc00->00a0000, 00e0000->0fffff are likely that) or ACPI tables and configuration data. I don't believe that this reserved memory is even counted in the the Memory: message.
____ david parsons \bi/ though I've been narrowly focusing on the mechanics \/ of the memory detection to the exclusion of all other kernel-side stuff.
- 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/
| |