lkml.org 
[lkml]   [2002]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: discontiguous memory platforms
Date
On Thursday 02 May 2002 10:50, Roman Zippel wrote:
> Hi,
>
> On Thu, 2 May 2002, Andrea Arcangeli wrote:
>
> > What I
> > care about is not to clobber the common code with additional overlapping
> > common code abstractions.
>
> Just to throw in an alternative: On m68k we map currently everything
> together into a single virtual area. This means the virtual<->physical
> conversion is a bit more expensive and mem_map is simply indexed by the
> the virtual address.

Are you talking about mm_ptov and friends here? What are the loops for?
Could you please describe the most extreme case of physical discontiguity
you're handling?

> It works nicely, it just needs two small patches in the initializition
> code, which aren't integrated yet. I think it's very close to what Daniel
> wants, only that the logical and virtual address are identical.

Yes, since logical and virtual kernel addresses in config_nonlinear differ
only by a constant (PAGE_OFFSET) then setting the constant to zero gives
me your case.

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.113 / U:1.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site