9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Re: Re: [9fans] system crash during compile
Date: Thu, 13 Jul 2006 07:52:00 -0700	[thread overview]
Message-ID: <7d3530220607130752x4a64235bk46d757de1f9d2ab@mail.gmail.com> (raw)
In-Reply-To: <63626928d1b9d7d7a5001593df460222@coraid.com>

On 7/13/06, Brantley Coile <brantley@coraid.com> wrote:
> > Swap has never worked.  It mostly works, but there have
> > always been hard-to-reproduce and then even harder-to-debug
> > little issues, and I just don't trust it at all.  With memory so
> > cheap, there is little motivation to fix it.
>
> That explains our mail processing problems that we had a few years ago
> when the incoming load was so high that it exceeded local store and we
> turned on swap, but things were still funky.  (wound up limiting the number
> of connections allowed to port 25 at a given time.)
>
> Might I suggest we remove swap from the system, at least remove it
> enough so people don't fall prey to it?
>
> I would argue backing store is a thing of the past and that Sandy
> Fraser's objections to the Plan 9 team early on, as I understand his
> objections to be, were correct.  Let's just use paging to manage the
> store in the box and to perhaps demand load text.  We're a long way
> from tiny, expensive local stores and slow drums.
>
> Let's just take it out.
>
Swap is handy. When you're running on 32 MB of RAM on an old laptop
that you don't want to spend on to upgrade, slow virtual memory is
better than nothing at all. I would volunteer to make swap work, but
it seems like it would be one of those things that's more deeply tied
to the rest of the system (which I don't know well); also, I don't
really know C.

John
--
TANSTAAFL! (There Ain't No Such Thing As A Free Lunch!)


      reply	other threads:[~2006-07-13 14:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 16:01 John Floren
2006-07-09 18:57 ` Russ Cox
2006-07-09 21:41   ` John Floren
2006-07-11  5:05     ` John Floren
2006-07-11  5:21       ` andrey mirtchovski
2006-07-11 15:15         ` John Floren
2006-07-11 18:41           ` Francisco J Ballesteros
2006-07-11 22:46             ` David Leimbach
2006-07-12  0:46               ` John Floren
2006-07-12  0:59                 ` andrey mirtchovski
2006-07-12 14:51                   ` John Floren
2006-07-12 21:10                     ` Russ Cox
2006-07-13  0:15                       ` John Floren
2006-07-13  0:17                         ` Francisco J Ballesteros
2006-07-13  2:27                           ` John Floren
2006-07-13  4:09                             ` Russ Cox
2006-07-13  4:10                               ` Russ Cox
2006-07-13 13:44                               ` Brantley Coile
2006-07-13 14:52                                 ` John Floren [this message]

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=7d3530220607130752x4a64235bk46d757de1f9d2ab@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).