[Top] [All Lists]

Re: [PATCH v2] Revert "MIPS: make CAC_ADDR and UNCAC_ADDR account for PH

To: Leonid Yegoshin <>
Subject: Re: [PATCH v2] Revert "MIPS: make CAC_ADDR and UNCAC_ADDR account for PHYS_OFFSET"
From: Ralf Baechle <>
Date: Wed, 26 Jun 2013 19:50:15 +0200
Cc: "Steven J. Hill" <>, "" <>, Florian Fainelli <>
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <> <> <> <> <>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Jun 26, 2013 at 04:50:03PM +0000, Leonid Yegoshin wrote:

> EVA has actually INCREASE in user address space - I right now run system with 
> 2GB phys memory and 3GB of user virtual memory address space. Work in 
> progress is to verify that GLIBC accepts addresses above 2GB.

I took the 0x40000000 for a KSEG0-equivalent because you previously
mentioned the value of 0x80000000.

> Yes, it is all about increasing phys and user memory and avoiding 64bits. 
> Many solutions dont justify 64bit chip (chip space increase, performance 
> degradation and increase in DMA addresses for devices).

Fair enough - but in the end the increasing size of metadata and pagetables
which has to reside in lowmem will become the next bottleneck and highmem
I/O performance has never been great, is on most kernel developers shit list
and performance optimizations for highmem are getting killed whenever they
are getting into the way.

So I'd say EVA gives you something like 1.5GB of memory at most with good
performance and a 2GB userspace and something like 0.5GB, maybe 0.75GB
with a 3GB userspace.  Beyond that you need highmem and that's where things,
especially kernel programming get more complicated and slower.


<Prev in Thread] Current Thread [Next in Thread>