From: Russell King <rmk@arm.linux.org.uk>
To: Roman Zippel <roman@augan.com>
Cc: Kanoj Sarcar <kanoj@google.engr.sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: pte_pagenr/MAP_NR deleted in pre6
Date: Fri, 11 Aug 2000 14:20:23 +0100 (BST) [thread overview]
Message-ID: <200008111320.OAA02445@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3993E87A.234FDEE7@augan.com> from "Roman Zippel" at Aug 11, 2000 01:50:18 PM
Roman Zippel writes:
> Can you send me that patch? I'd like to check it, if it can be used for
> the m68k port. m68k still has its own support for discontinous mem and
> from what I've seen so far I'm not really convinced yet to give it up.
I don't see anything wrong in continuing with this. ARM also does
this in addition to support for the discontig mem stuff. Why?
The generial discontig code is ok so long as you have a lot of RAM
in node 0. However, since all allocations currently come from node
0, if this node is small, then there is a chance that you will run
out of memory at bootup, and then not be able to continue (and
because we both use fbcon, there is no message visible to the user,
and hence no diagnostics).
Continuing with the single node but many "areas" that ARM follows, and
from what it sounds like m68k does, means that you can allocate from
any "area", and therefore don't hit this restriction.
One way out of this would be if the NUMA stuff can have the "allocations
only from node 0" feature turned off, and then I'd be happy to let the
ARM version be replaced totally by the discontig case.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-08-11 13:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 17:18 pte_pagenr/MAP_NR deleted in pre6 Kanoj Sarcar
2000-08-11 2:24 ` David S. Miller
2000-08-14 0:34 ` Anton Blanchard
2000-08-11 11:50 ` Roman Zippel
2000-08-11 13:20 ` Russell King [this message]
2000-08-11 14:56 ` Roman Zippel
2000-08-12 9:18 ` Bjorn Wesen
2000-08-11 17:21 ` Kanoj Sarcar
2000-08-14 9:29 ` Roman Zippel
2000-08-15 16:19 ` Stephen C. Tweedie
2000-08-16 8:25 ` Roman Zippel
2000-08-16 17:13 ` Kanoj Sarcar
2000-08-16 18:20 ` Stephen C. Tweedie
2000-08-16 18:24 ` David S. Miller
2000-08-16 19:53 ` Stephen C. Tweedie
2000-08-16 18:47 ` Kanoj Sarcar
2000-08-16 18:39 ` David S. Miller
2000-08-16 19:30 ` Stephen C. Tweedie
2000-08-16 22:22 ` Kanoj Sarcar
2000-08-17 9:11 ` Stephen C. Tweedie
2000-08-17 19:07 ` Kanoj Sarcar
2000-08-17 19:01 ` David S. Miller
2000-08-17 19:19 ` Alan Cox
2000-08-17 19:20 ` David S. Miller
2000-08-17 19:33 ` Alan Cox
2000-08-17 19:36 ` Kanoj Sarcar
2000-09-07 14:31 ` Ralf Baechle
2000-08-17 19:50 ` Kanoj Sarcar
2000-08-17 19:41 ` David S. Miller
2000-09-07 14:26 ` Ralf Baechle
2000-08-17 19:56 ` Alan Cox
2000-08-17 19:24 ` Alan Cox
2000-08-17 19:32 ` Kanoj Sarcar
2000-08-17 19:30 ` David S. Miller
2000-08-17 20:00 ` Kanoj Sarcar
2000-08-16 18:17 ` Stephen C. Tweedie
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=200008111320.OAA02445@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=roman@augan.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