The Linux TCP/IP Stack: Networking for Embedded Systems (Networking Series) (Networking Series)
ASIN: 1584502843
Average Customer Review: 4.5, based on 7 reviews.
Customer reviews (5 of 7)
Not comprehensive, 2007-09-01, Rating: 3.
This book is not good to understand TCP/IP stack in Linux. The book has not gone through review for wrong section references. I have seen references mentioning to Chapter 4 when it actually is Chapter 7.
It never explains the main processing of TCP like cwnd update and sshthresh. After reading the whole book I still didnt understand what is done in TCP like which function does what.
A complete failure to qualify as a good book.
I suggest "Understanding Linux Network Internals" which explains very clearly what is done in IP. I expect that the author of that book comes up with a second volume that deals with TCP.
It never explains the main processing of TCP like cwnd update and sshthresh. After reading the whole book I still didnt understand what is done in TCP like which function does what.
A complete failure to qualify as a good book.
I suggest "Understanding Linux Network Internals" which explains very clearly what is done in IP. I expect that the author of that book comes up with a second volume that deals with TCP.
A trully admirable accomplishment - must have type of book, 2005-08-15, Rating: 5.
Before you spend your time and money on purchasing any books on the subject, buy this one first. Depending on your background and your needs, it may also be the last one you will purchase.
At the time I got to place my two-cent's worth, there are already 5 other reviews rating this book in a very positive light.
While the style of presentation of a technical subject may not be strictly original, there have been few attempts by other authors to use it, this author has actually delivered - very effectively.
Technical writers, take a note of this work - it can serve as a blueprint for other technical subjects. Publishers, please a take note of the style and the thoroughness that this work employs to present a complex technical subject. The demand is there - the competition is very scarce.
Yes, this book presents a comprehensive technical explanation in a very practical as well as theoretical terms, and more importantly, places all the components of the technology subject matter within context. After you get through this book you will not be left in a position where you sit in front of your computer and realize you really have no idea how to apply the knowledge of the book you just read. Instead, you will be off and running. Think back, how many books that you read in the past delivered this kind of ability to you?
In closing, I appeal to the author of this book to select another subject of the current technology and write another book. Sadly, the bookshelves are full of "bibles", "primers", and definitive guides that leave the reader wondering what to do AFTER they read them.
If you need to know how to DO networking, this book is a must.
At the time I got to place my two-cent's worth, there are already 5 other reviews rating this book in a very positive light.
While the style of presentation of a technical subject may not be strictly original, there have been few attempts by other authors to use it, this author has actually delivered - very effectively.
Technical writers, take a note of this work - it can serve as a blueprint for other technical subjects. Publishers, please a take note of the style and the thoroughness that this work employs to present a complex technical subject. The demand is there - the competition is very scarce.
Yes, this book presents a comprehensive technical explanation in a very practical as well as theoretical terms, and more importantly, places all the components of the technology subject matter within context. After you get through this book you will not be left in a position where you sit in front of your computer and realize you really have no idea how to apply the knowledge of the book you just read. Instead, you will be off and running. Think back, how many books that you read in the past delivered this kind of ability to you?
In closing, I appeal to the author of this book to select another subject of the current technology and write another book. Sadly, the bookshelves are full of "bibles", "primers", and definitive guides that leave the reader wondering what to do AFTER they read them.
If you need to know how to DO networking, this book is a must.
An Excellent book and covers the 2.6 kernel, 2005-06-14, Rating: 5.
This is an excellent book which explains everything related to the TCP/IP Linux implementation in the 2.6 kernel. There are other excellent Linux networking books, but this is the best one in terms of the details for the TCP/IP implementation.
It explains in detail Network devices, drivers, UDP, TCP, IP and IPv6. And it shows in detail all the steps a packet goes through when moving from the application layer to the socket layer, then through the transport layer (TCP or UDP), Network Layer (IP) and Data Link Layer and finally to the physical layer. Then it shows the details of the flow of the packet at the receiving side.
It explains in detail Network devices, drivers, UDP, TCP, IP and IPv6. And it shows in detail all the steps a packet goes through when moving from the application layer to the socket layer, then through the transport layer (TCP or UDP), Network Layer (IP) and Data Link Layer and finally to the physical layer. Then it shows the details of the flow of the packet at the receiving side.
OK, but poorly written, 2005-03-04, Rating: 4.
Loads of info, all's good, but it's a struggle. I mean, explanations don't match the pictures, a lot of redundancies in the text (that make you wonder if perchance they're not redundancies and force you to backtrack -- to no avail, 'cause they *are* redundancies); strange hyphenation habits ("pre-pending and removal"... well, then make it "re-moval", be consistent, at least... "pre-allocated", "de-allocated", etc.); on one line it's "sk_buff" on the next it's "skb" -- I mean THIS IS NOT POETRY! This is a lot of precise, dumb and boring literal-minded stuff that, in order to be understood, HAS TO BE RIGHT! every time, all the time). p.256, "The array of frags is placed in memory ... It can contain as many as six pages in the array." In which array? Does this mean IT ITSELF contains six pages of memory, or does mean that it happens to be in possession of yet another array -- and it is this other array that holds the aforementioned memory pages?
OK, it is an unfortunate fact of life that techies are massively deprived of the aptitude for verbal communication, fine, but where's the editor? It's a fifty-dollar book, for chrissakes. The book is very irritating in this respect.
Otoh, it's got a lot of good stuff, so, in a paroxysm of charitableness, I'll give it four stars after all. But it's darn hard to read, 'cause the author, though he knows his stuff, is an inarticulate turdhead, and the editor took a nap -- 'cause, you know, you'll buy it anyway, why bother.
Four stars, but only this time.
PS. Be sceptical about the review by John Matlock "Gunny" (right below here). This guy cannot possibly have read what he's reviewed; to convince yourself, please visit his reviews page and count the number of reviews he posts daily, every day, since the beginning of time. A dozen of all-positive reviews every day -- yeah, I believe he's read these books. Buyer beware ("Gunny" is not alone: there are quite a few "reviewers" like that on Amazon these days; when you see one of those "Top Reviewers", be sceptical, check their reviewing record; I've seen people reviewing over a hundred books per day every day; others re-type a cover blurb or table of contents; there's a lot of smart alecks of this sort, so watch out).
PPS. A couple of things I forgot to mention, but probably should have: first, there's nothing specifically embedded in this book; and second, there's a similar O'Reilly Linux networking book that is by an order of magnitude better. I didn't have it when I wrote this review (which was more than a year ago), but now I do and can compare. I forget the title off the top of my head, but search for it, it's easy to find. If I were writing a review for this book today, I'd not give it more than three stars -- though again, there's got a lot of good info in it: the book isn't bad technically, just confusingly written.
OK, it is an unfortunate fact of life that techies are massively deprived of the aptitude for verbal communication, fine, but where's the editor? It's a fifty-dollar book, for chrissakes. The book is very irritating in this respect.
Otoh, it's got a lot of good stuff, so, in a paroxysm of charitableness, I'll give it four stars after all. But it's darn hard to read, 'cause the author, though he knows his stuff, is an inarticulate turdhead, and the editor took a nap -- 'cause, you know, you'll buy it anyway, why bother.
Four stars, but only this time.
PS. Be sceptical about the review by John Matlock "Gunny" (right below here). This guy cannot possibly have read what he's reviewed; to convince yourself, please visit his reviews page and count the number of reviews he posts daily, every day, since the beginning of time. A dozen of all-positive reviews every day -- yeah, I believe he's read these books. Buyer beware ("Gunny" is not alone: there are quite a few "reviewers" like that on Amazon these days; when you see one of those "Top Reviewers", be sceptical, check their reviewing record; I've seen people reviewing over a hundred books per day every day; others re-type a cover blurb or table of contents; there's a lot of smart alecks of this sort, so watch out).
PPS. A couple of things I forgot to mention, but probably should have: first, there's nothing specifically embedded in this book; and second, there's a similar O'Reilly Linux networking book that is by an order of magnitude better. I didn't have it when I wrote this review (which was more than a year ago), but now I do and can compare. I forget the title off the top of my head, but search for it, it's easy to find. If I were writing a review for this book today, I'd not give it more than three stars -- though again, there's got a lot of good info in it: the book isn't bad technically, just confusingly written.
An Excellent Introduction for an Engineer, 2005-01-18, Rating: 5.
This is an in-depth guide to implementing and using the Linux TCP/IP stack. It begins with a general overview of TCP/IP networking, with background information on applicable networking standards. From there, it details the TCP/IP implementation in Linux by following a pack of data as it flows through the stack from the sending system, out the wire, and back through the input side of the stack in the receiving machine. This unique approach gives programmers an inside look at the entire process.
The book is aimed at th engineers and programmers implementing dedicated or embedded systems including sockets, network interfaces, application protocols and practical considerations.
The CD included with the book includes the source code developed in the book, much of which can be modified to fit many quasi-standard applications, and a considerable amount of additional technical information on Linux and the particular aspects of TCP/IP.
The book is aimed at th engineers and programmers implementing dedicated or embedded systems including sockets, network interfaces, application protocols and practical considerations.
The CD included with the book includes the source code developed in the book, much of which can be modified to fit many quasi-standard applications, and a considerable amount of additional technical information on Linux and the particular aspects of TCP/IP.
Projects