All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Valdis.Kletnieks@vt.edu, Tomasz Chmielewski <mangoo@wpkg.org>,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	Byron Stanoszek <bstanoszek@comtime.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hugh@veritas.com>
Subject: Re: 2.6.32-rc3: low mem - only 378MB on x86_32 with 64GB. Why?
Date: Mon, 5 Oct 2009 17:30:51 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0910051727420.3432@localhost.localdomain> (raw)
In-Reply-To: <b6a2187b0910051715y4ee63503y148ba2d7e24cad8e@mail.gmail.com>



On Tue, 6 Oct 2009, Jeff Chua wrote:
> 
> Loud and clear. And appreciated all the replies. I think it's time for
> upgrade!

As Byron said, it really should be sufficient to just upgrade the kernel 
(I presume that you already have a CPU that is 64-bit capable: not very 
many boards with old CPU's can even fit 64GB of ram).

In fact, I wish more people did that, just so that we'd get better 
coverage of the 32-bit compat code. We occasionally find issues there, 
although I think it's getting rarer.

			Linus

  parent reply	other threads:[~2009-10-06  0:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 15:57 2.6.32-rc3: low mem - only 378MB on x86_32 with 64GB. Why? Jeff Chua
2009-10-05 18:12 ` Linus Torvalds
     [not found]   ` <b6a2187b0910051715y4ee63503y148ba2d7e24cad8e@mail.gmail.com>
2009-10-06  0:30     ` Linus Torvalds [this message]
2009-10-06 10:06       ` Tvrtko Ursulin
2009-10-06 11:01         ` Frans Pop
2009-10-14 21:32           ` Lennart Sorensen
2009-10-06 12:59       ` David Woodhouse
2009-10-06 14:26         ` Linus Torvalds
2009-10-11  9:08           ` Benjamin Herrenschmidt
     [not found]       ` <b6a2187b0910052312o662642b2teded3d19548b9151@mail.gmail.com>
2009-10-06 14:35         ` Linus Torvalds
     [not found]           ` <b6a2187b0910080926x303d3c9em8f70632fb19b6509@mail.gmail.com>
2009-10-08 16:35             ` Dave Hansen
     [not found]           ` <b6a2187b0910090928r648169dax86178a3e8b8c2f21@mail.gmail.com>
2009-10-10 18:10             ` Valdis.Kletnieks
2009-10-10 18:37               ` Linus Torvalds
2009-10-11  9:06           ` Benjamin Herrenschmidt
2009-10-11 17:34             ` Linus Torvalds
2009-10-06 16:50   ` Yuhong Bao
2009-10-05 18:42 ` Byron Stanoszek
2009-10-05 19:15 ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2009-10-05 19:42 Tomasz Chmielewski
2009-10-05 20:31 ` Valdis.Kletnieks
     [not found] <drYiu-Pj-15@gated-at.bofh.it>
2009-10-05 20:05 ` Daniel J Blueman

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=alpine.LFD.2.01.0910051727420.3432@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=bstanoszek@comtime.com \
    --cc=daniel.blueman@gmail.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=hugh@veritas.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.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 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.