Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Aug 2008 01:24:04 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Robert Watson <rwatson@freebsd.org>, Marko Zec <zec@FreeBSD.org>,  freebsd-virtualization@freebsd.org, Alan Cox <alc@cs.rice.edu>
Subject:   next moves
Message-ID:  <48A7E024.3040705@elischer.org>

next in thread | raw e-mail | index | archive | help
My thoughts..

once commit2 is committed and effectively becomes -current, then 
commit3 and commit1 could be done, which would reduce the diff size more

it:
1/ adds Marco's real include files and the real final definitions of
V_ vars.

2/ adds a bunch of the final INIT_VNET_XXX macros in place
to further reduce the size of the binaries

3/ introduces (but does not yet use) the structures that hold the globals


after this we should STILL see no real binary change.

If we could get the same horsepower on commit3 that we have seen on 
commit2 then I see no reason it would not be in a committable state
in a few days.. the next step after that would be to do the
vimage-commit branch, which after the commit3 branch was added
would be a small additional step. It adds a few more of the
macros but is aimed at pure diff reduction it may follow just
a day or so after commit3. It's an incremental change, but is
derived from the vimage branch rather than from the commit2 
(mechanical) branch, and basically just acts as a shim in
diff to get us a bit closer to where we are going.




Once those branches have been committed I would suggest a
step where turnign on VIMAGE actually doesn't enable vimage entirely,
but simply enables global versions of the structures mentionned above.
This would be the step that Brook was looking for. constructors woudl 
be used. Destructors less so.

We would do some timing tests at this point to quantify the relative
speeds of global and  "structified" versions. As ALC has pointed out,
it is possible we may want to tune the structures.

The last vimage step would be to switch on the  virtualisatin 
framework and commit the remainder of the vimage branch (modulo
cleanups and what we learn in the mean while).

after that I think we turn our attention to the jail sets
work that James is doing..









Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48A7E024.3040705>