On Thu, 2 May 2002, Daniel Phillips wrote:
> I'll accept 'not needed for 68K', though I guess config_nonlinear will work
> perfectly well for you and be faster than the loops. However, some of the
> problems that config_nonlinear solves cannot be solved by any existing kernel
> mechanism. We've been over the NUMA-Q and mips32 cases in detail, so I won't
> reiterate.
Maybe I missed that, but could you give me an example of a memory
configuration, which would be difficult to handle with the current
vm? Could you describe, how in your model the physical address space would
be mapped to the logical and virtual address space and how they are mapped
into the pgdat nodes?
Some real numbers would help me a lot to understand, what you have in
mind. I have a rough idea of it, but I want to be sure we are talking
about the same thing.
bye, Roman
-
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/