From: Chris Wedgwood <cw@f00f.org>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
MM mailing list <linux-mm@kvack.org>,
linux-kernel@vger.rutgers.edu,
"Stephen C. Tweedie" <sct@redhat.com>,
Christoph Rohland <hans-christoph.rohland@sap.com>
Subject: Re: [patch] zoned-2.3.28-G5, zone-allocator, highmem, bootmem fixes
Date: Sun, 14 Nov 1999 22:32:39 +1300 [thread overview]
Message-ID: <19991114223239.A1332@caffeine.ix.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.10.9911141110480.1278-100000@chiara.csoma.elte.hu>; from Ingo Molnar on Sun, Nov 14, 1999 at 11:16:40AM +0100
> the solution is to:
>
> -#include <asm/pgtable.h>
> +#include <asm/pgalloc.h>
> we do not want to put #ifdef CONFIG_X86-type of stuff into the main
> kernel.
pgalloc.h only exists fof x86 -- so this won't work
> > > - fixed boot task's swapper_pg_dir clearing
> >
> > what else needs to be done to alloc the buffer cache to use the low
> > 16MB?
>
> fallback from 'highmem => normalmem => dmamem' should work already.
stupid question perhaps, but how can I verify this...
> will have a look - i think we are simply out of balance somewhere,
ok, perhaps this is it -- should drivers and the swap code need to
know about the zone stuff and explicity do things differently?
-cw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-11-14 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-13 19:22 [patch] zoned-2.3.28-G4, " Ingo Molnar
1999-11-13 21:33 ` [patch] zoned-2.3.28-G5, " Ingo Molnar
1999-11-13 22:06 ` Chris Wedgwood
1999-11-14 10:16 ` Ingo Molnar
1999-11-14 9:32 ` Chris Wedgwood [this message]
1999-11-14 10:43 ` Ingo Molnar
1999-11-14 12:17 ` Russell King
1999-11-14 14:22 ` Ingo Molnar
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=19991114223239.A1332@caffeine.ix.net.nz \
--to=cw@f00f.org \
--cc=hans-christoph.rohland@sap.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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