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 16:00, Roman Zippel wrote:
> Hi,
>
> On Wed, 1 May 2002, Daniel Phillips wrote:
>
> > > 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?
>
> It simply searches through all memory nodes, it's not really efficient.
>
> > Could you please describe the most extreme case of physical discontiguity
> > you're handling?
>
> I can't assume anything. I'm thinking about calculating the table
> dynamically and patching the kernel at bootup, we are already doing
> something similiar in the Amiga/ppc kernel.

Maybe this is a good place to try out a hash table variant of
config_nonlinear. It's got to be more efficient than searching all the
nodes, don't you think?

--
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.081 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site