* new directory structure in doc/devel to take RFC's
rfc/ - Final RFC's
rfc_pending/ - Emerging RFC's
rfc_dropped/ - Rejected or Parked RFC's
* Template directory doc/template/ for just a rfc.txt
for creating new RFC's yet
* admin/rfc.sh a script to maintain RFC's
Describes some of the design decisions and rationales in a rather sketchy
way explained. New Developers may find this Document useful to get an idea
about how the different components work together.
We will need cluster/page aligned access for certain files (indices),
this files will contain an initial header describing the contents. A bias
is used to step over this header and align the following data.
This generates very terse Documentation for hardcopies
* All official docs are included
* No Graphs
* No internal, TODO, BUGS, etc. docs
* No inlined sources
This generates a detailed documentation in html_browse/
* all things get extracted (undocumented, TODO, BUG etc...)
* produces a warnings_browse.txt to show undocumented things
* no graphs to keep it reasonable small
As on the nov2008 developer meeting we concluded that the normal
Documentation shall have less noise and reflect the actual project state.
Further we will introduce special Doxyfiles for special tasks.
* backend.filehandles maximum filehandles used
* backend.mmap_window_size mapping window start size
* backend.as_limit address space limit
This needs to be changed to use the lumieraorg_configuration interface.
Quite some code which was hold back in favor of the config and plugin stuff
implements:
* mmapcache: mru cache for unused memory mappings
* mmap: single mmaped areas
* mmapings: manages mmaps established for one filedescriptor
