On 28.03.2017 00:36, Andres Rodriguez wrote:
Depending on usage patterns, the current LRU policy may create a
non-injective mapping between userspace ring ids and kernel rings.
This behaviour is undesired as apps that attempt to fill all HW blocks
would be unable to reach some of them.
This
Forgot to add
v2: compressed ring_blacklist (nha)
On 2017-03-27 06:36 PM, Andres Rodriguez wrote:
Depending on usage patterns, the current LRU policy may create a
non-injective mapping between userspace ring ids and kernel rings.
This behaviour is undesired as apps that attempt to fill all HW
On 2017-03-23 08:02 AM, Nicolai Hähnle wrote:
On 17.03.2017 19:52, Andres Rodriguez wrote:
Depending on usage patterns, the current LRU policy may create a
non-injective mapping between userspace ring ids and kernel rings.
This behaviour is undesired as apps that attempt to fill all HW
On 17.03.2017 19:52, Andres Rodriguez wrote:
Depending on usage patterns, the current LRU policy may create a
non-injective mapping between userspace ring ids and kernel rings.
This behaviour is undesired as apps that attempt to fill all HW blocks
would be unable to reach some of them.
This
