On Fri, Jan 26, 2018 at 05:16:02PM +0300, Ilya Maximets wrote:
> On 26.01.2018 15:00, Stokes, Ian wrote:
> > Hi All,
> >
> > Recently an issue was raised regarding the move from a single shared
> > mempool model that was in place up to OVS 2.8, to a mempool per port model
> > introduced in 2.9.
> -Original Message-
> From: Kevin Traynor [mailto:ktray...@redhat.com]
> Sent: Friday, January 26, 2018 3:48 PM
> To: Ilya Maximets ; Stokes, Ian
> ; ovs-discuss@openvswitch.org
> Cc: Flavio Leitner ; Loftus, Ciara
>
hOn 01/26/2018 03:16 PM, Ilya Maximets wrote:
> On 26.01.2018 15:00, Stokes, Ian wrote:
>> Hi All,
>>
>> Recently an issue was raised regarding the move from a single shared mempool
>> model that was in place up to OVS 2.8, to a mempool per port model
>> introduced in 2.9.
>>
>>
On 26.01.2018 15:00, Stokes, Ian wrote:
> Hi All,
>
> Recently an issue was raised regarding the move from a single shared mempool
> model that was in place up to OVS 2.8, to a mempool per port model introduced
> in 2.9.
>
>
Hi All,
Recently an issue was raised regarding the move from a single shared mempool
model that was in place up to OVS 2.8, to a mempool per port model introduced
in 2.9.
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-January/046021.html
The per port mempool model was introduced in