News for hackers. Stuff that matters.
Re:Anatomy of a Program in Memory by moxy on Tuesday January 27, 2009 @02:43PM (#452600)
I'd like to understand what's being described in this article, but unfortunately I lack the necessary educational background. Does anyone have any links to other resources that will allow me to better understand what is being discussed in this post?
Re:Anatomy of a Program in Memory by wmf on Tuesday January 27, 2009 @05:23PM (#452877)
Virtual memory is part of the fields of computer architecture and operating systems; popular textbooks are Computer Architecture: A Quantitative Approach and Modern Operating Systems.

http://books.google.com/books?id=pqYl3SWkA64C http://books.google.com/books?id=tqtZGQAACAAJ

Re:Anatomy of a Program in Memory by narag on Tuesday January 27, 2009 @04:13PM (#452738)
CPUs prior to 386 had direct access to physical memory. From 386 on, you could enable protected mode (default for Linux and Windows 95+) in which a pointer doesn't point to a physical location but to a virtual address that system translates to physical memory or disk-cached memory. That's the most basic fact. With much luck, that's the only thing you need to know to understand it :-)
Re:Anatomy of a Program in Memory by brl on Tuesday January 27, 2009 @03:19PM (#452648)
This article is already a very high level description of Linux memory management (specifically on 32 bit Intel processors). If you want to move down to lower levels of abstraction and learn more details, then keep reading that blog! On the other hand, if you want a less technical description of these concepts then I'm not sure where to look.