On 3/13/2012 1:29 AM, Roland Dreier wrote:
It's just a heuristic, but I figured some app might want to register
essentially all of memory, and then we want some more to cover other
users. The amount of memory used for unused MTT space is pretty small,
I think.
If an app registered
On Mon, Mar 12, 2012 at 11:27 PM, Or Gerlitz ogerl...@mellanox.com wrote:
If an app registered essentially all memory, then practically nothing else
left for other users, or you refer to the case where the driver consumed an
MTT segment made of 8 elements on behalf of a certain app but didn't
On Mon, Mar 5, 2012 at 8:09 PM, Roland Dreier rol...@kernel.org wrote:
Handle this by having the driver allocate at least enough MTT entries to
cover 2 * totalram pages.
just curious, why we want to cover totalram? also the commit title
has mxl4 instead of mlx4
Or.
--
To unsubscribe from this
On Mon, Mar 12, 2012 at 2:35 PM, Or Gerlitz or.gerl...@gmail.com wrote:
just curious, why we want to cover totalram? also the commit title
has mxl4 instead of mlx4
It's just a heuristic, but I figured some app might want to register essentially
all of memory, and then we want some more to
From: Roland Dreier rol...@purestorage.com
The current driver defaults to 1M MTT segments, where each segment holds
8 MTT entries. This limits the total memory registered to 8M * PAGE_SIZE
which is 32GB with 4K pages. Since systems that have much more memory
are pretty common now (at least
From: Roland Dreier rol...@purestorage.com
The current driver defaults to 1M MTT segments, where each segment holds
8 MTT entries. This limits the total memory registered to 8M * PAGE_SIZE
which is 32GB with 4K pages. Since systems that have much more memory
are pretty common now (at least
