Re: fork: out of memory

[david parsons]

In article <[e-mail]>,
Zlatko Calusic  <[e-mail]> wrote:
>Jan Echternach <[e-mail]> writes:
>
>> On 28 November 1997, Alan Cox <[e-mail]> wrote:
>> > This is silly. You can already guarantee your DMA allocations and waste
>> > less memory than that by compiling drivers in rather than as modules
>> 
>> Compiling a driver statically into the kernel is not always an option.
>> Maybe you're short on memory, or you want to fiddle with some compile-
>> time options or debug the driver without rebooting once in a minute.
>> 
>
>So, you're short of 20,30 KB for driver, and thus decide to allocate
>(mostly) unused 128 or even 256 KB (to be sure DMA requests always
>succeed), so that you can load your driver?

  If you're bumping up against kernel image size limits, it seems like a
  reasonable trade-off (I do this as a matter of course for my
  single-floppy installers, because I need to wedge about 90 SCSI
  drivers into the image and, even if I did go to a bzimage instead of a
  zimage, I'd still run out of room on a 1.44mb floppy if I added in too
  many additional drivers.)

                ____
  david parsons \bi/ Gimme a BIOS hd.c and I could get wads of install space
                 \/                                                     back.