Memory Management: Algorithms and Implementations In C/C++ (Windows Programming/Development)

Having read other reviews, I will agree that the material in the last chapter is just a little prophetic.


If you didn't know, now you know   January 14, 2003
O. Durojaiye (Bellevue, WA United States)
3 out of 4 found this review helpful

Look out for the name Bill Blunden if you're a systems programmer. In my opinion this man will be one of the best known authors in this area in the next decade. I bought this book thinking all I will get was details on garbage collection algorithms but the author actually takes the reader through memory management at the hardware level in an easy to follow manner. He also reviews how 3 different operating systems actually manage memory.

After this, he then jumps into the high level details of memory management for applications.

If you're a system programmer, do yourself a favour and buy this book. However, it should be noted that this book is not for the inexperienced. It digs into low level stuff and also assumes that the reader is fluent in C/C++ and assembly.


The whole enchillada!   January 20, 2003
7 out of 10 found this review helpful

This is probably the only book I have ever bought that actually gave a discussion on protected mode that I could follow. He does keep the discussion basic (flat model, no paging), but it got me over the hurdle.

I also liked his high-level memory managers. They were to the point and easy to understand. No fancy syntax, no cryptic pointer swizzling,... just straightforward code. What Blunden provides is a solid foundation that has a low learning threshold.

Finally, Blunden speaks to the reader in a casual manner, as if you were sipping high-octane coffee somewhere on El Camino BigNum.


No holds barred (NHB programming)   January 20, 2003
4 out of 8 found this review helpful

As a public servant involved in technical copyright work, I normally don't stray too far from my area of specialy. However, a friend of mine recommended this book and I picked it up at a local bookstore.

This book does a nice job of looking at the countless little details that come into play when dealing with a computer's memory. What was once very easy for hackers to fiddle with in 1981 is now a nasty ordeal. Fortunately you'll have this book to guide you.

Nice explanation of the A20 address gate.

One thing I didn't expect was a look behind all the marketing hype behind Moore's Law. The last chapter is somewhat ominous, and it makes you wonder if the author has been to John Young's web site. TIA is closer than you think...


Developmental history and some examples of Code   July 22, 2004
Mark W Mitchell (Roswell, GA USA)
6 out of 6 found this review helpful

This book, is one of the few computer books I have read from cover to cover - code listings are easy to scan/skip, and the book itself is not huge (however the cost seems fairly high for the size).

This book is clearly written, and well researched. It is not for beginners.

This book spends time on the hardware aspects of Memory management based on the Intel 386 and above architecture. Real Mode versus protected mode and how the processor design allows for memory protection in protected mode.

This is then followed by a survey of Operating Systems, from DOS to Linux to Windows - which is moving from the simple to the complex - and how the OS provides Memory Management services.

Then the development of computer languages, and how they allow for memory management starting with COBOL and moving on to Object oriented C++ and Java Virtual Machines.

Finally the last part of the book has a lot of code listings with very simplistic memory management and moving into slightly more complex algorithms for memory management for programs. The focus is on introducing multiple approaches and how to measure the real performance of each - some parts of this part of the book seemed like they were repeating the same text in making comments about the code.

Overall, I liked the book. I read the Pentium Protected Mode architecture book last year, and it prepared me for this book.
I have not done much assembly level x86 programming, but enough to understand what was being shown in the early examples.

The book has a very good bibilography of sources for each chapter - six long chapters. I felt, while looking at these bibilographies, that the time spent in going through all of the items in the bibliography was part of the reason that this books price was set so high. The references here are thorough and identify some turning points in computer sciences to me.

The structure of the book is the layers by which memory managment is accomplshed - the memory management code is more of an intro. I felt that the book might be targeting Computer Science courses as its real market - the books structure lays down a good foundation for further exploration.

The deeper development of Memory Management algorithms is where I too found the book lacking, and the title a bit deceiving - a complaint from another that I would agree with. This is the reason for not giving 5 stars. It would have taken a lot more time to develop the code and write explanations for more complex approaches and the author states this repeatedly in this algorithm section of the book.

I am inspired from this book to learn more about x86 assembly language, and to study the actual code of the Linux Kernel.
If that sounds of interest to you too, then you should buy this book.