m>;
> ovs-dev@openvswitch.org; ovs-disc...@openvswitch.org; Robert Wojciechowicz
> <robertx.wojciechow...@intel.com>; Ian Stokes <ian.sto...@intel.com>; Ilya
> Maximets <i.maxim...@samsung.com>; Kavanagh, Mark B
> <mark.b.kavan...@intel.com>
> S
es <ian.sto...@intel.com>; Ilya
Maximets <i.maxim...@samsung.com>; Kavanagh, Mark B <mark.b.kavan...@intel.com>
Subject: Re: [ovs-dev] mbuf pool sizing
On 01/23/2018 11:42 AM, Kevin Traynor wrote:
> On 01/17/2018 07:48 PM, Venkatesan Pradeep wrote:
>> Hi,
>>
On 01/23/2018 11:42 AM, Kevin Traynor wrote:
> On 01/17/2018 07:48 PM, Venkatesan Pradeep wrote:
>> Hi,
>>
>> Assuming that all ports use the same MTU, in OVS2.8 and earlier, a single
>> mempool of 256K buffers (MAX_NB_MBUF = 4096 * 64) will be created and shared
>> by all the ports
>>
>> With
On 01/17/2018 07:48 PM, Venkatesan Pradeep wrote:
> Hi,
>
> Assuming that all ports use the same MTU, in OVS2.8 and earlier, a single
> mempool of 256K buffers (MAX_NB_MBUF = 4096 * 64) will be created and shared
> by all the ports
>
> With the OVS2.9 mempool patches, we have port specific
Hi,
Assuming that all ports use the same MTU, in OVS2.8 and earlier, a single
mempool of 256K buffers (MAX_NB_MBUF = 4096 * 64) will be created and shared by
all the ports
With the OVS2.9 mempool patches, we have port specific allocation and the
number of mbufs created for each port is based
