From: Victor Yodaiken <yodaiken@fsmlabs.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Victor Yodaiken <yodaiken@fsmlabs.com>,
Andrea Arcangeli <andrea@suse.de>,
Benjamin LaHaise <bcrl@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mempool design
Date: Tue, 18 Dec 2001 09:06:06 -0700 [thread overview]
Message-ID: <20011218090606.A4786@hq2> (raw)
In-Reply-To: <20011217083802.A25219@hq2> <Pine.LNX.4.33.0112181753230.3753-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0112181753230.3753-100000@localhost.localdomain>
On Tue, Dec 18, 2001 at 05:55:14PM +0100, Ingo Molnar wrote:
>
> On Mon, 17 Dec 2001, Victor Yodaiken wrote:
>
> > I agree with all your arguments up to here. But being able to run
> > Linux in 4Meg or even 8M is important to a very large class of
> > applications. [...]
>
> the amount of reserved RAM should be very low. Especially in embedded
> applications that usually have a very controlled environment, with a low
> number of well-behaving devices, the number of pages needed to be reserved
> is very low. I wouldnt worry about this.
Bueno.
next prev parent reply other threads:[~2001-12-18 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 19:40 mempool design Ingo Molnar
2001-12-15 18:47 ` Benjamin LaHaise
2001-12-15 22:18 ` Ingo Molnar
2001-12-17 15:04 ` Andrea Arcangeli
2001-12-17 15:38 ` Victor Yodaiken
2001-12-17 16:10 ` Andrea Arcangeli
2001-12-17 17:33 ` kernel panic Geoffrey
2001-12-18 16:55 ` mempool design Ingo Molnar
2001-12-18 16:06 ` Victor Yodaiken [this message]
2001-12-17 17:21 ` Ingo Molnar
2001-12-17 15:58 ` Andrea Arcangeli
2001-12-18 0:32 ` Rik van Riel
2001-12-18 15:21 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-12-15 9:01 Ingo Molnar
2001-12-15 15:39 ` 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=20011218090606.A4786@hq2 \
--to=yodaiken@fsmlabs.com \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.