linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Piet Delaney <piet@www.piet.net>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VM docs and where they are going
Date: 15 Jul 2003 13:48:46 -0700	[thread overview]
Message-ID: <1058302126.19468.882.camel@www.piet.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0307141634090.24480@skynet>

On Tue, 2003-07-15 at 03:20, Mel Gorman wrote:

Thanks Mel, your monographs looks extremely interesting.
I'll be reading them for weeks.

Is there a similar document for the rest of the 2.5/2.6 kernel;
something to supplement Bovet's & Cesati's book on understanding the
linux kernel. I'll finish my subscription to the LKDP mailing list.

I studied John Lion's UNIX commentary back and your 
Linux VM commentary is a greatly appreciated. 

-piet


> I made a small number of typo corrections and expanded the introduction
> chapter a small bit on the Linux VM docs on my site. The changes are small
> enough that if anyone has already printed it out, don't bother printing it
> again. They are still available from the usual places.
> 
> Main document
> PDF:  http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/understand.pdf
> HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/understand/
> Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/understand.txt
> 
> Code commentary
> PDF:  http://www.csn.ul.ie/~mel/projects/vm/guide/pdf/code.pdf
> HTML: http://www.csn.ul.ie/~mel/projects/vm/guide/html/code/
> Text: http://www.csn.ul.ie/~mel/projects/vm/guide/text/code.txt
> 
> On the where it's going front from here, I'm happy to say I've now writing
> a book which will be published under the Bruce Peren's Open Book Series
> (http://www.perens.com/Books/). Some stuff that I'm working on for it
> include;
> 
> o Better integration of the code commentary so it's easier to follow
> o Much better introduction sections and updating of the software tools
> o Shiny CD that comes with softcopy versions of the docs, browsable
>   version of the tree and hopefully online call graph generation
> o Chapter on anonymous shared memory including the virtual filesystem
> o Assorted expansions and additions
> o And best of all, a fairly detailed introduction to 2.6. The 2.6 sections
>   are at the end of each chapter and give a fairly detailed account
>   (right now, it's totalling about 30 pages) of what is new in 2.6 and
>   how it is implemented
> 
> If all goes well, it'll be available before the end of this year or in
> early 2004 :-)
> 
> -- 
> Mel Gorman
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
-- 
piet@www.piet.net

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2003-07-15 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 10:20 Mel Gorman
2003-07-15 20:48 ` Piet Delaney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1058302126.19468.882.camel@www.piet.net \
    --to=piet@www.piet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox