From: David Weinehall <tao@acc.umu.se>
To: David Luyer <david_luyer@pacific.net.au>
Cc: "'Oliver Xymoron'" <oxymoron@waste.org>, linux-kernel@vger.kernel.org
Subject: Re: vm philosophising
Date: Sat, 19 Jan 2002 06:46:14 +0100 [thread overview]
Message-ID: <20020119064613.C18492@khan.acc.umu.se> (raw)
In-Reply-To: <007601c1a0a4$9ddc5d70$46943ecb@pacific.net.au>
In-Reply-To: <007601c1a0a4$9ddc5d70$46943ecb@pacific.net.au>; from david_luyer@pacific.net.au on Sat, Jan 19, 2002 at 03:49:02PM +1100
On Sat, Jan 19, 2002 at 03:49:02PM +1100, David Luyer wrote:
> I wrote:
> > Alan Cox wrote:
> > > > There is another VM that has a property that people would like:
> > > > deterministically handling memory exhaustion.
> > > > Unfortunately, that VM
> > > > probably can't co-exist with over-commit and the
> > > > performance gains that
> > > > affords.
> > >
> > > It can definitely co-exist. Overcommit control is just a
> > > book keeping
> > > exercise on address space commits.
>
> [...]
>
> and the comment I somehow missed putting on the end:
>
> If you want to philosophise about VM strategies, think of
> overcommit as "ethernet" and precommit as "token ring".
You mean, that while technically superior, precommit suffers from
a topological problem and the fact that a very expensive concentrator
is needed?! ;-)
Token Ring still lives in the spirit, though it's called FDDI
nowadays...
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2002-01-19 5:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 4:49 vm philosophising David Luyer
2002-01-19 5:46 ` David Weinehall [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-18 4:30 Rik spreading bullshit about VM Bosko Radivojevic
2002-01-18 4:36 ` vm philosophising Rik van Riel
2002-01-18 4:58 ` Matthew Johnson
2002-01-18 5:12 ` Rik van Riel
2002-01-18 5:18 ` Ryan Cumming
2002-01-18 5:43 ` Matthew Johnson
2002-01-21 17:55 ` Bill Davidsen
2002-01-18 6:05 ` Matthew Johnson
2002-01-18 14:42 ` Tommy Faasen
2002-01-18 15:52 ` listmail
2002-01-21 15:50 ` The Doctor What
2002-01-21 16:16 ` Mike Harrold
2002-01-18 15:55 ` Mr. Shannon Aldinger
2002-01-18 18:39 ` Oliver Xymoron
2002-01-18 19:23 ` Alan Cox
2002-01-18 20:17 ` David Schwartz
2002-01-18 21:39 ` Alan Cox
2002-01-19 4:42 ` David Luyer
2002-01-19 18:00 ` Rob Landley
2002-01-20 5:42 ` Stevie O
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=20020119064613.C18492@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=david_luyer@pacific.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
/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