From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-mm <linux-mm@kvack.org>
Cc: John Alvord <jalvo@cloud9.net>, Jan Echternach <jec@DInet.de>,
Mike Jagdis <mike@roan.co.uk>,
linux-kernel@vger.rutgers.edu
Subject: Re: fork: out of memory
Date: Thu, 27 Nov 1997 14:35:31 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971127143242.746A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.OSF.3.95.971127130913.4485D-100000@ruunat.fys.ruu.nl>
On Thu, 27 Nov 1997, Rik van Riel wrote:
> > Memory is getting so inexpensive in some environments, wouldn't it make
> > sense to have an option to reserve DMA-able memory at init time? With 16
> > megs going for $60, it is worth setting aside 4megs or 8 megs which would
> > have to be specially requested.
>
> 128 k would be enough, the largest DMA buffer allocated by devices
> is 64k in size (soundcard) and ftape uses 3 32k area's. the scsi
On second thought, it doesn't need to be completely free... If
we can also use it for cache/buffer memory... Kicking that out
when we can't find a 64kB area for DMA memory might be bad for
performance (temporarily), but since it is good for stability,
it is a Good Thing (any system outperforms a crashed system :)
in search of a Better Thing (tm),
Rik.
----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
next parent reply other threads:[~1997-11-27 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.OSF.3.95.971127130913.4485D-100000@ruunat.fys.ruu.nl>
1997-11-27 13:35 ` Rik van Riel [this message]
[not found] <199712040152.RAA00762@belvdere.vip.best.com>
1997-12-04 9:37 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.91.971127143242.746A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=jalvo@cloud9.net \
--cc=jec@DInet.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mike@roan.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox