[Chapter Feedback & Discussion] "Programming Persistent Memory: A Comprehensive Guide for Developers" Book

92 views
Skip to first unread message

Steve Scargall

unread,
Aug 14, 2019, 11:13:25 AM8/14/19
to pmem
This is the thread to discuss and provide feedback on the chapters for our "Programming Persistent Memory: A Comprehensive Guide for Developers" book.

We are requesting your feedback - good or bad.  We hope that you love it, but if something doesn't make sense or is unclear, seems wrong, code doesn't compile, you found a typo or grammatical error, etc. we want to know.  And this is the place to do it.  It would be helpful to provide the following information with your feedback:

Chapter#
Page#
Quote the section of the text or reference a figure, table, or code listing

Thanks in advance

    Steve


Yahya H. Mirza

unread,
Dec 19, 2019, 5:51:45 PM12/19/19
to pmem
Hi Steve,

Just started to go through your book in detail.  I looked at your book a while back and there was only a single chapter or so online. I recently saw a reference to your book and was excited to see it was all done!  At first glance it looks like a great read and I'm looking forward to digging in.

For comments, while I can add them here, it might be easier to add comments directly in the word document for each of the chapters assuming you are using Word.
Regardless, per your request, I will post my reviews here as I read each of the chapters.

Chapter: 1
Page:     8

"The libpmemobj library is a full-featured transaction and allocation library for persistent memory. We describe libpmemobj in more detail in Chapter and its C++ cousin in Chapter 8. If you are unable to find data structures that meet your needs, the most likely approach you will take is to implement what you need using this library as described in Chapter 11."

Small nitpick, it is not clear if you meant that the description of libpmemobj as well as its C++ cousin is described in Chapter 8, or if there is another Chapter for libpmemobj, separate of Chapter 8 which you left blank possibly as a place holder when you were writing the chapter?

Yahya Mirza
Aclectic Systems Inc.

Steve Scargall

unread,
Dec 20, 2019, 10:28:04 AM12/20/19
to pmem
Thanks Yahya,

Each library within the PMDK or associated with persistent memory programming, such as libmemkind, has a dedicated chapter.  libpmemobj and libpmemobj-cpp have their own dedicated chapter.  However, libpmemobj-cpp is really just some C++ header files to wrap libpmemobj, so the statement applies to both libpmemobj and libpmemobj-cpp.

We fixed a few typos, grammatical issues, and technical clarification in the final round of reviews.  These changes are not reflected in the early preview I posted to https://pmem.io/book/.  

The book is available for pre-order through Amazon, Barnes & Nobel, Apress, and others.  I'm expecting the digital version to be available next week and the printed copies should be available around New Year.  We missed getting the book out for stocking stuffers.  Sorry about that.

/Steve


Yahya H. Mirza

unread,
Dec 23, 2019, 7:09:21 PM12/23/19
to pmem
Steve,

Would it still be useful to provide feedback on new online version of the chapters that goes live this week?

Had I known you were so far along, I would of reviewed the chapters earlier!

Regardless, I'm going through the chapters now.  I hope to finish the book by the Persistent Memory Summit.

Yahya

Steve Scargall

unread,
Dec 23, 2019, 7:41:01 PM12/23/19
to pmem
Thanks Yahya,

I would wait for the book release since we made edits in the final proof.  There's not a lot of changes, but I wouldn't want you to spend time reviewing old content and I can't make any further changes to the book since it's now in the print queue.  Feedback on the final version of the book is always welcome as we can roll it into the 2nd edition.

Attendees of the SNIA Persistent Memory Summit and Persistent Memory Programming Hackathon/Workshops can pick up a free digital copy of the book on a USB drive, or download a free copy from Apress. If anyone brings a physical copy, the contributors and I will be happy to sign it. 

Steve
Reply all
Reply to author
Forward
0 new messages