From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Frans Pop <elendil@planet.nl>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
torvalds@linux-foundation.org, jeff.chua.linux@gmail.com,
Valdis.Kletnieks@vt.edu, mangoo@wpkg.org,
daniel.blueman@gmail.com, bstanoszek@comtime.com,
dave@linux.vnet.ibm.com, hugh.dickins@tiscali.co.uk,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
hugh@veritas.com
Subject: Re: 2.6.32-rc3: low mem - only 378MB on x86_32 with 64GB. Why?
Date: Wed, 14 Oct 2009 17:32:57 -0400 [thread overview]
Message-ID: <20091014213257.GA5498@csclub.uwaterloo.ca> (raw)
In-Reply-To: <200910061301.39221.elendil@planet.nl>
On Tue, Oct 06, 2009 at 01:01:35PM +0200, Frans Pop wrote:
> Tvrtko Ursulin wrote:
> >> 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.
> >
> > Maybe convince some distro to offer this setup as an option at least? I
> > always wondered why no one has, or maybe I missed it.
>
> Debian has a 64-bit kernel for its 32-bit "i386" architecture (and also for
> its 64-bit "amd64" architecture obviously):
> - for stable: http://packages.debian.org/lenny/linux-image-2.6.26-2-amd64
> - for unstable: http://packages.debian.org/sid/linux-image-2.6.30-2-amd64
I have been running that Debian setup for 5 years now. It's great.
Other than 32 bit iptables not liking the 64bit kernel, I can't currently
recall any issues at any point. Well and configure scripts often have to
be run with the 'linux32' wrapper to make them not try something stupid.
--
Len Sorensen
next prev parent reply other threads:[~2009-10-14 21:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 15:57 Jeff Chua
2009-10-05 18:12 ` Linus Torvalds
[not found] ` <b6a2187b0910051715y4ee63503y148ba2d7e24cad8e@mail.gmail.com>
2009-10-06 0:30 ` Linus Torvalds
2009-10-06 10:06 ` Tvrtko Ursulin
2009-10-06 11:01 ` Frans Pop
2009-10-14 21:32 ` Lennart Sorensen [this message]
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
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=20091014213257.GA5498@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--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=elendil@planet.nl \
--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 \
--cc=torvalds@linux-foundation.org \
--cc=tvrtko.ursulin@sophos.com \
/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
all inboxes | Powered by JetHome®