On 6/26/2018 9:30 PM, Aaron Conole wrote:
Hi Ian,
Ian Stokes writes:
This commit re-introduces the concept of shared mempools as the default
memory model for DPDK devices. Per port mempools are still available but
must be enabled explicitly by a user.
OVS previously used a shared mempool
Hi Ian,
Ian Stokes writes:
> This commit re-introduces the concept of shared mempools as the default
> memory model for DPDK devices. Per port mempools are still available but
> must be enabled explicitly by a user.
>
> OVS previously used a shared mempool model for ports with the same MTU
>
On 06/26/2018 07:59 PM, Ian Stokes wrote:
>>
>>> -/* Tries to allocate a new mempool - or re-use an existing one where
>>> - * appropriate - on requested_socket_id with a size determined by
>>> - * requested_mtu and requested Rx/Tx queues.
>>> - * On success - or when re-using an existing
On 6/26/2018 3:33 PM, Kevin Traynor wrote:
On 06/25/2018 12:56 PM, Ian Stokes wrote:
This commit re-introduces the concept of shared mempools as the default
memory model for DPDK devices. Per port mempools are still available but
must be enabled explicitly by a user.
OVS previously used a
On 06/25/2018 12:56 PM, Ian Stokes wrote:
> This commit re-introduces the concept of shared mempools as the default
> memory model for DPDK devices. Per port mempools are still available but
> must be enabled explicitly by a user.
>
> OVS previously used a shared mempool model for ports with the
This commit re-introduces the concept of shared mempools as the default
memory model for DPDK devices. Per port mempools are still available but
must be enabled explicitly by a user.
OVS previously used a shared mempool model for ports with the same MTU
and socket configuration. This was replaced
