VM documentation

VM documentation

[Mel Gorman]

Yet another release in the usual places. The main reasons for the release
is a correction on the subject of vmalloc more than anything else and the
rearrangement of chapters to present the material in more logical order. I
am hoping there will only be one, or at most two more releases after this
before it's done and dusted (famous last words).

Understanding the Linux Virtual Memory Manager
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

Few important reasons for this release but still, it brings me closer to
just finalising it and releasing it fully.

1. Chapters have been rearranged a little so there should be no forward
   references left and the material is handled in an "easier" order for
   understanding it. Each chapter now has an introduction as well so it
   isn't as clunky to read at parts

2. I messed up the explanation of vmalloc by saying pages are allocated at
   fault time rather than saying that it is just the page tables for the
   faulting process are synced with the master page tables. Pretty serious
   mistake so anyone looking at vmalloc stuff should re-read

3. Minor correction on the explanation of try_to_free_pages() in the code
   commentary. I now explain why it only frees up pages in ZONE_NORMAL

4. Loads of polish like font and grammar corrections. Minor mistake in
   slab where I said /proc/cpuinfo instead of /proc/slabinfo and a few
   others like that

-- 
Mel Gorman
MSc Student, University of Limerick
http://www.csn.ul.ie/~mel

Building a 2.4.x kernel with all options

[Henrique Gobbi]

Dear all !!!

Is there a easy way to compile a linux 2.4 kernel with all possible 
options. That is, something like "make all" or "make everything".

I need to build a kernel that has everything set. If possible I'd like 
to use everything that can be module as module.'

Any hint is welcome
-- 
regards
Henrique

Re: Building a 2.4.x kernel with all options

[Jörn Engel]

On Tue, 18 March 2003 11:15:05 +0000, Henrique Gobbi wrote:
> 
> Is there a easy way to compile a linux 2.4 kernel with all possible 
> options. That is, something like "make all" or "make everything".
> 
> I need to build a kernel that has everything set. If possible I'd like 
> to use everything that can be module as module.'
> 
> Any hint is welcome

There is no easy way, there isn't even a single "biggest .config".
Some drivers are mutually exclusive, so you have to chose.

Tomorrow at work, I can send you a .config that should have almost
everything compiled into the kernel, for i386 uniprocessor, linux
2.4.21-pre3.

If you manage to create an even bigger .config from that base or have
other maxed our configs for smp, other platforms or other kernels, I'd
like to get a copy. But make sure they compile first. :)

Jörn

-- 
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is needed for all of them.

Re: Building a 2.4.x kernel with all options

[Jörn Engel]

On Tue, 18 March 2003 22:20:29 +0100, Jörn Engel wrote:
> 
> Tomorrow at work, I can send you a .config that should have almost
> everything compiled into the kernel, for i386 uniprocessor, linux
> 2.4.21-pre3.

I found a couple more. Have a look at
http://wohnheim.fh-wedel.de/~joern/software/kernel/configs/

make vmlinux should work for all of them, if not, please drop in a
mail.

Jörn

-- 
Ninety percent of everything is crap.
-- Sturgeon's Law