=20
- Low memory heap (useful to move code off kern/i386/pc/startup.S)=
=2E
=20
Originally I thought of a path relocator32-relocator users-mm
relocator32 is ready for next round of review but is untested. Now I=
think about it mm patch isn't actually dependent on relocator32,
On Sun, Aug 16, 2009 at 09:35:37PM +0200, Vladimir 'phcoder' Serbinenko wrote:
Actually I don't understand why it was proposed to include it in 1.97
at all - it changes memory management, bugs in it are likely to be
critical and benefit is only smaller core. If it was up to me I would
just
I have this thingie available at my git branches mm and mm+move but
it needs more testing. Unless it's tested enough it should be
postponed and not included in 1.97.
Actually I don't understand why it was proposed to include it in 1.97
at all - it changes memory management, bugs in it are likely
On Wed, Aug 12, 2009 at 02:45:19PM +0200, Vladimir 'phcoder' Serbinenko wrote:
- Low memory heap (useful to move code off kern/i386/pc/startup.S).
Originally I thought of a path relocator32-relocator users-mm
relocator32 is ready for next round of review but is untested. Now I
think
But available memory is several orders of magnitude bigger than the largest
block a loader will need. So is this really an issue?
It's not always the case. Two examples
1) Solaris. At least some distributions of solaris use a big (70 MiB
compressed, around 200 MiB compressed) initrd which has
- Low memory heap (useful to move code off kern/i386/pc/startup.S).
Originally I thought of a path relocator32-relocator users-mm
relocator32 is ready for next round of review but is untested. Now I
think about it mm patch isn't actually dependent on relocator32, just
you won't get some
