Russell King wrote:
> > 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?
My problem is that I'm not really familiar with the high memory support.
The problem here is that the relation between virtual address / physical
address / page struct / memmap+index is hardly documented and it gets
more interesting when a page struct might also represent an i/o area
(for direct i/o).
> 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).
Another problem on m68k: I can make almost no assumption about the
memory layout to play some clever tricks. If I remember correctly I had
some problems with the memmap layout, since lots of code assumed a
continuos memmap and there were some tricks to get the above
relationship right.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:24 EST