Hi Jan/Pradeep,
Thanks for flagging this issue, I hadn't considered it before. I agree that
this needs to be investigated further.
If it's of use I have reverted the per port mempool patches manually for
testing with the head of master so that both approaches can be checked against
these type
Hi Pradeep,
Yes, this is for sure a bug in the current OVS mempool handling (and possibly
in many other DPDK applications). In the past it was perhaps not so critical
because shared mempools rarely got released, but with per port mempools it
becomes a real threat. And as you say, we do not
