svn commit: r298230 - in head: lib/libstand sys/boot/common sys/boot/efi/libefi sys/boot/efi/loader sys/boot/i386/libfirewire sys/boot/i386/libi386 sys/boot/i386/loader sys/boot/mips/beri/loader sy...

[Maxim Sobolev]

Sorry, if stupid question, but can this feature kick in automatically once
you have more than X MB amount of memory available, going back to default
memory-conserving "slow" mode if not? I cannot imagine that would take too
much effort/code to implement.

I take care of some really old legacy embedded systems at customer
> sites, and even so, with stuff dating back to the 2003-ish timeframe,
> the smallest i386 memory I have to deal with is 64MB.  Are there really
> x86 systems that need to run in 32MB or less of ram these days, and use
> BIOS or EFI to boot?
>

Ian, let's not forget that there are lot of VM systems out there these
days. If you run very narrow functionality image but your app needs to run
zillion of them you might want to dial down VM memory size to a bare
minimum. Still those VM system often use just the regular i386 loader bits.
So, yes, it's possible that some people might actually run amd64 or i386
kernels on very small RAM footprints even today.

-Max