Conversation
OK so that, minus descriptions of things like mprotect(), madvise(), mremap() and general review and cleanup is process memory done.

Been working on this part of the book (initially I thought it'd be 1 chapter, lol) for at least 6 months.

After a month of basically no book progress due to being away for lsf/mm and ill this is a great relief and keeps me on time after my last reschedule of targets.

Next: OOM killer chapter which, when done, will be released as a sample chapter.
2
1
6
@DrHyde Maybe :) though I suspect the one I plan to do on 'practical memory management' which will be geared towards helping real life stuff might be more useful.

Most of the book is stupidly detailed dives into code otherwise
1
0
1
@ljs but you do know describing mremap() is at least a week worth of work, right?
1
0
1
@vbabka why the fuck do you think I'm deferring that f-ing stupid function? 🤣
1
0
1
@vbabka not sure why I swore out loud on first one then not on second but mremap() does that to a person
0
0
1
@DrHyde probably a bit of both ;) but we'll see.
0
0
0