public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Google's mm problem - not reproduced on 2.4.13
Date: Wed, 31 Oct 2001 14:53:31 -0700	[thread overview]
Message-ID: <20011031145331.S16554@lynx.no> (raw)
In-Reply-To: <E15yzlQ-00021P-00@starship.berlin> <E15z28m-0000vb-00@starship.berlin> <20011031214540.D1291@athlon.random> <E15z2WJ-0000wc-00@starship.berlin>
In-Reply-To: <E15z2WJ-0000wc-00@starship.berlin>; from phillips@bonn-fries.net on Wed, Oct 31, 2001 at 10:03:31PM +0100

On Oct 31, 2001  22:03 +0100, Daniel Phillips wrote:
> Ben reports that his test with 2 Gig memory runs fine, as it does for me, but 
> that it locks up tight with 3.5 Gig, requiring power cycle.  Since I only 
> have 2 Gig here I can't reproduce that (yet).

Sadly, I bought some memory yesterday, and it was only U$30 for 256MB
DIMMs, so $120/GB if you have enough slots.  Not that I'm suggesting
you go out and but more memory Daniel, as you probably have your slots
filled with 2GB, and larger sticks are still bit more expesive.

The only thing that bugs me about the low memory price is that Windows
XP recommends at least 128MB for a workable system.  A year or two ago
that would have been considered a bloated pig, but now they are giving
away 128MB DIMMs with a purchase of XP.  Sad, really.  Maybe M$ is
subsidizing the chipmakers to make RAM cheap so XP can run on peoples'
computers ;-)?  What else would you do with U$50 billion in cash (or
whatever) that M$ has?

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-10-31 21:54 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 18:06 Google's mm problem - not reproduced on 2.4.13 Daniel Phillips
2001-10-31 20:39 ` Daniel Phillips
2001-10-31 20:45   ` Andrea Arcangeli
2001-10-31 21:03     ` Daniel Phillips
2001-10-31 21:53       ` Andreas Dilger [this message]
2001-11-01  4:52         ` Daniel Phillips
2001-11-01 16:56           ` undefined reference in 2.2.19 build with Reiserfs (was: Google's mm problem - not reproduced on 2.4.13) Sven Heinicke
2001-11-01 22:39             ` Keith Owens
2001-10-31 22:12       ` Google's mm problem - not reproduced on 2.4.13 Ben Smith
2001-11-01  0:34         ` Andrea Arcangeli
2001-11-02 17:51         ` Sven Heinicke
2001-11-02 18:00           ` Andrea Arcangeli
2001-11-02 18:19             ` Daniel Phillips
2001-11-02 20:27               ` Linus Torvalds
2001-11-02 21:08                 ` Ben Smith
2001-11-02 21:20                   ` Linus Torvalds
2001-11-02 22:42                     ` Ben Smith
2001-11-02 23:15                       ` Daniel Phillips
2001-11-03 22:53                       ` Adaptec vs Symbios performance Stephan von Krawczynski
2001-11-03 23:01                         ` arjan
2001-11-02 21:12                 ` Google's mm problem - not reproduced on 2.4.13 Rik van Riel
     [not found]               ` <200111022027.fA2KRwe20006@penguin.transmeta.com>
2001-11-02 20:58                 ` Daniel Phillips
2001-11-02 18:11           ` Daniel Phillips
2001-11-02 18:48             ` Sven Heinicke
2001-11-02 18:57               ` Daniel Phillips
2001-11-01  0:19     ` Daniel Phillips
2001-11-01  0:29       ` Andrea Arcangeli
2001-11-01  1:17       ` Ben Smith
2001-11-01  1:41         ` Rik van Riel
2001-11-01  1:55           ` Ben Smith
2001-11-01  2:06             ` Andrea Arcangeli
2001-10-31 20:48   ` Rik van Riel
2001-10-31 21:04     ` Daniel Phillips
2001-10-31 21:08       ` Rik van Riel
     [not found] <Pine.LNX.4.33.0111021250560.20078-100000@penguin.transmeta.com>
2001-11-02 21:13 ` Linus Torvalds
2001-11-02 21:27   ` Stephan von Krawczynski
2001-11-03  0:16     ` Linus Torvalds

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=20011031145331.S16554@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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