Peter T wrote:
> is there already a workaround to only see the capped memory from within the
> zone? A lot of apps check for available memory first and try to get as much
> as possible. If every zone returns the total system memory, logical result
> is bad performance in the zones and leakage to swap.
No. This is bug:
6564672 capped memory in zone not visible as capped
zones-discuss mailing list