From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Andi Kleen <ak@suse.de>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Henti Smith <bain@tcsn.co.za>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: maximum possible memory limit ..
Date: Mon, 28 Apr 2003 15:40:25 -0700 [thread overview]
Message-ID: <20030428224025.GW30441@holomorphy.com> (raw)
In-Reply-To: <483810000.1051549109@[10.10.2.4]>
At some point in the past, Dave Hansen wrote:
>> Each one of those needs to be audited before pgcl is acceptable to a
>> wide audience. We've already seen plenty of stuff that breaks. ext2/3
>> look to be all right, but I know that JFS is broken.
On Mon, Apr 28, 2003 at 09:58:31AM -0700, Martin J. Bligh wrote:
> Well, the upside is that he's only doing s/PAGE_SIZE/MMU_PAGESIZE/
> in most places, which are normally both 4K. So it will have no effect
> whatsoever unless you explicitly turn it on.
The JFS issue is general to PAGE_SIZE > 4KB, pgcl-induced or not. shaggy
et al are already aware of it.
Most of the driver stuff I've seen is ioremap() of O(PAGE_SIZE) which
just gets denied so it fails to probe. IDE was worse (as usual), and
AGP needed an unusual amount of tweaking, which probably will be
typical for the graphics drivers in general. Block stuff seems to be
well-abstracted, so basically the only semantically significant needed
fix for block drivers is for 512*q->max_len < PAGE_SIZE (not yet done).
-- wli
next prev parent reply other threads:[~2003-04-28 22:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 18:05 maximum possible memory limit Henti Smith
2003-04-24 18:35 ` Valdis.Kletnieks
2003-04-28 13:08 ` Carl-Daniel Hailfinger
2003-04-28 14:10 ` [Lse-tech] " Andi Kleen
2003-04-28 15:11 ` Carl-Daniel Hailfinger
2003-04-28 15:16 ` Andi Kleen
2003-04-28 16:52 ` Dave Hansen
2003-04-28 16:58 ` Martin J. Bligh
2003-04-28 22:40 ` William Lee Irwin III [this message]
2003-04-28 23:50 ` Dave Jones
2003-04-29 0:00 ` William Lee Irwin III
2003-04-29 0:06 ` Dave Jones
2003-04-29 0:13 ` William Lee Irwin III
2003-04-28 22:34 ` William Lee Irwin III
2003-04-28 22:33 ` William Lee Irwin III
2003-04-29 4:02 ` William Lee Irwin III
2003-04-28 16:45 ` Dave Hansen
2003-04-28 16:57 ` Carl-Daniel Hailfinger
2003-04-28 17:13 ` Andi Kleen
2003-04-28 17:53 ` David Mosberger
2003-04-28 18:31 ` Gerrit Huizenga
2003-04-28 19:05 ` David Mosberger
2003-04-28 17:16 ` Dave Hansen
2003-04-28 17:36 ` Carl-Daniel Hailfinger
2003-04-28 17:44 ` Andi Kleen
2003-04-28 22:43 ` William Lee Irwin III
2003-04-28 22:43 ` William Lee Irwin III
2003-04-28 18:57 ` Anton Blanchard
2003-04-28 17:14 ` Andi Kleen
2003-04-28 17:26 ` Dave Hansen
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=20030428224025.GW30441@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=bain@tcsn.co.za \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.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