From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Jones <davej@codemonkey.org.uk>,
"Martin J. Bligh" <mbligh@aracnet.com>,
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 17:13:19 -0700 [thread overview]
Message-ID: <20030429001319.GB30441@holomorphy.com> (raw)
In-Reply-To: <20030429000602.GA32260@suse.de>
On Mon, Apr 28, 2003 at 05:00:14PM -0700, William Lee Irwin III wrote:
>> AGP was fiddling around with something, which very well may
>> have been some kind of GART aperture for all I know about it, and needed
>> to use MMUPAGE_SIZE to think of its size correctly.
On Tue, Apr 29, 2003 at 01:06:02AM +0100, Dave Jones wrote:
> A lot of GARTs can only operate on 4KB pages. As long as this is kept in
> mind, things should tick along just fine. Even those that can operate
> with different size pages, we still treat as 4KB.
That's basically the gist of it. The "larger page" is purely a software
construct anyway, so the search and replace approach should be fine.
i.e. s/PAGE_SIZE/MMUPAGE_SIZE/ for the appropriate bits of GART drivers
It won't fix the issues with true hardware page sizes of larger than
4KB, but the issues raised by the larger software page size (really
get_free_pages() allocation unit) are very fixable there.
-- wli
next prev parent reply other threads:[~2003-04-29 0:01 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
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 [this message]
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=20030429001319.GB30441@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=bain@tcsn.co.za \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=davej@codemonkey.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).