<< 1 >>
Rating:  Summary: One of the very best technical books I own Review: I buy a lot of technical books - more than I could possibly ever read. This title is, for me, very readable. The Author presents information the way I want to see it. I really like the historical background information on Linux and comparisons to Unix. If you are looking for one single reference on Linux programming, I recommend this title. Not just for kernel hacking.
Rating:  Summary: Excellent Linux kernel development book for newbie and prof. Review: I have been doing Linux kernel/system level development on and off since 1999. This is the book that I think should be owned by any Linux newbie who wants starting their kernel hacking. Even if people do not directly do Linux kernel development, it is a good book complementary to any serious operating systems course in college - it helps gain a better idea of how and why.
The book is quite easy to follow and read and does not try to overwhelm readers with tons of information (consequently it does not address many details in Linux kernel). I consider this is a major strength of the book which parts away from other books (comparing to "Understanding the Linux Kernel", which has quite some details on each subsystem, but if you take the book as your guide to kernel programming, you feel you are overwhelmed by the information and often clueless on where to start to write some simple stuffs. This does not mean I think the latter is a bad one - it is a very good one indeed). Considering the fact that Linux kernel evolves so fast, it may make sense to focus on the core parts and once you understand them, it may become easy for you to track and understand changes later. Even as a professional programmer doing kernel development, occasionally referencing a well-written book like this is very helpful.
I am a bit reluctant to rate it 5 stars though due to many typos observed, which I guess is the result of rush to publishing (and the poor job of proofreading). Fortuanately, most can be understood by reading the contexts around them. But a few are really misleading or totally wrong. For example, on page 169, there is a sample code to show how page allocation/free is done in kernel. It uses __get_free_pages() to allocate pages, but uses free_pages() to free these pages. As the author has just said a page ago, __free_pages() should be used to free (struct page*) pages, otherwise corruption will ensure (free_pages is used to free pages with logic address as parameter).
Rating:  Summary: good book on Linux 2.6 kernel programming Review: I just got the book today. I feel deceived in that the details about this book stated around 500 pages. Given the price, I figured this was a reasonable price/page ratio. Now that I have the book in hand, I realize it's only 330 pages, including index and stuff.I guess this is more of a beef with Amazon than the book.
Rating:  Summary: Great book Review: I like the book because it is well organized, clear, no nonsense, explains the subject top-down, up-to-date including kernel 2.6, contains very little code and despite the subject still readable as a regular book. It is like a book about operating systems in general but about Linux only. I'd recommend reading this book before "Understanding the Linux Kernel". However, I find the word "Development" in the title a little misleading because the book contains very little about the actual howto and could have been backed up by for example an appendix with an example from real life with a step-by-step walk-thru by the hand.
Rating:  Summary: clear and careful explanations from an expert Review: I was a Linux kernel newbie writing a device driver and started reading "Linux Device Drivers" by Rubini. On hindsight, this was a bad idea. Rubini's book goes deep into driver code quickly with good details but it only sparingly touches the higher level kernel overview or essential concepts. These missing pieces are covered very well in Love's book and I should have understood them before reading Rubini's book; important basic concepts covered in good detail include: - user thread vs kernel thread. - kernel-space process context vs kernel-space interrupt context. - tasklet as a non-concurrent form of softirq and is not related in any way to tasks. - bottom-half methods comprising softirq, tasklet and work queue; and that BH and task queue are obsolete and deprecated. - semaphore sleeping vs spinlock spinning (busy-wait). - spinlock adversely affecting scheduling latency while semaphore does not. Love's book shows ambly that he is an expert in Linux kernel matters and speaks with authority. At the same time he has the ability of a good teacher to explain obscure and critical kernel concepts clearly. I heartily recommend this as the first book one should read about the Linux kernel, well before books such as Bovet's "Understanding the Linux Kernel" or Rubini's device driver book.
Rating:  Summary: A must read book for kernel developpers Review: The author is really a good teacher. He gradually takes the reader into the dark woods of kernel and still assures the ease of understanding the programming concepts well.You really feel the joy of evolving into a professional as you read this book.Kudos. I own it.
Rating:  Summary: Excellent Read Review: There is only 1 reason that I didn't give this book a 5 star rating. I found the memory management a bit below par. But that's probably because the initial chapters up the bar so high that the last few fail to live up to those high standards. The chapter on Scheduling is phenomenal - easily the best! Maybe even that is an understatement. An added "advantage" is that this book is on kernel 2.6. If you're entering the realm of kernel hacking, my recommendation is, read this first, Linux device Drivers by Rubini next, and then Understanding the Linux Kernel by Bovet and Cesati. What next? The source - that's where you'll get all the answers. :)
Rating:  Summary: Amazing book Review: This book dives into the structure of the kernel and how it works in great details. It doesn't lose you in technicalities like some books, instead Robert Love keeps it as close to simple english as possible and tries to make it very easy to read.
I've never read a book that taught me so much about the kernel's inner workings in just the first 3 chapters. I've now read about half of them and will probably finish it today. This book is truly amazing.
Rating:  Summary: clear and careful explanations from an expert Review: This is a good book to know kernel internals, good explanations with irqsoft(syscall) versus workqeues ant tasklets, context proces versus fork and thread .... Good joob
Rating:  Summary: Great technical book Review: This is a very easy introduction to hacking on the linux kernel, there is not much discussion about design choices, but it explains how the kernel work, how to program on it and what things one need to look out for. The book is readable for both newbies and uber kernel hackers and through out the book Robert has a great sense of humor that most other technical books does not have. Highly recomended read.
<< 1 >>
|