From: Ingo Molnar <mingo@chiara.csoma.elte.hu>
To: Russell King <rmk@arm.linux.org.uk>
Cc: cw@f00f.org, torvalds@transmeta.com, linux-mm@kvack.org,
linux-kernel@vger.rutgers.edu, sct@redhat.com,
hans-christoph.rohland@sap.com
Subject: Re: [patch] zoned-2.3.28-G5, zone-allocator, highmem, bootmem fixes
Date: Sun, 14 Nov 1999 15:22:18 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.9911141441050.3555-100000@chiara.csoma.elte.hu> (raw)
In-Reply-To: <199911141217.MAA00054@raistlin.arm.linux.org.uk>
On Sun, 14 Nov 1999, Russell King wrote:
> Ingo Molnar writes:
> > no. The zone stuff is completely transparent, all GFP_* flags (should)
> > work just as before. All interfaces were preserved. So shortly before 2.4
> > it is not acceptable to break established APIs. (neither is it necessery)
>
> Except discontiguous memory systems, which I've now got a real bad
> headache for and am currently resorting to a fixed zone-size until the
> new stuff can be fixed. Dunno if this is going to work yet, since the
> free watermarks are going to be just wrong.
interfacing the zone configuration to the lowlevel memory configuration is
not yet fully worked out.
do you see any conceptual problem with the current zoned allocator?
-- mingo
--
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/
prev parent reply other threads:[~1999-11-14 14:22 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
1999-11-14 10:43 ` Ingo Molnar
1999-11-14 12:17 ` Russell King
1999-11-14 14:22 ` Ingo Molnar [this message]
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=Pine.LNX.4.10.9911141441050.3555-100000@chiara.csoma.elte.hu \
--to=mingo@chiara.csoma.elte.hu \
--cc=cw@f00f.org \
--cc=hans-christoph.rohland@sap.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=rmk@arm.linux.org.uk \
--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