[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1255252133.2192.38.camel@pasglop>
Date: Sun, 11 Oct 2009 20:08:53 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: David Woodhouse <dwmw2@...radead.org>,
Jeff Chua <jeff.chua.linux@...il.com>, Valdis.Kletnieks@...edu,
Tomasz Chmielewski <mangoo@...g.org>,
Daniel J Blueman <daniel.blueman@...il.com>,
Byron Stanoszek <bstanoszek@...time.com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hugh@...itas.com>
Subject: Re: 2.6.32-rc3: low mem - only 378MB on x86_32 with 64GB. Why?
On Tue, 2009-10-06 at 07:26 -0700, Linus Torvalds wrote:
> The Intel Xorg guys used to do everything in 32-bit kernels because they
> were also testing that they didn't break compatibility (which is a big
> deal with that whole crazy DRM-in-kernel/direct-rendering-in-user-space
> thing) and seemingly didn't realize that the compat layer was _supposed_
> to mean that they could run a 64-bit kernel and still have a working
> 32-bit land.
>
> It's driver interfaces like that that tend to break. ioctl's etc. But I
> have heard less noise about it lately, so I do think it's mostly working.
I'm running a 32-bit Ubuntu karmic distro with a 64-bit kernel on my
thinkpad and so far, I yet have to encounter a single obvious problem
due to the compat layer. Everything seems to work fine including 3D,
compiz fancyness in X etc... :-)
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists