Hi Mahdi, This patch should apply, ACL plugin had not seen much changes recently, but then you are not running a 20.05 anymore :-)
I would strongly suggest to evaluate on what limitations prevent you from following the master branch as close as possible and address them. This may seem daunting, but based on my experience with a dozen or so scenarios, following master is the most sustainable and flexible approach in the long term. With the current API compatibility process that went into action shortly past 20.05, *if* you are using VPP as is, 20.09 should be a ~zero-cost move that you can evaluate (there are only 2 incompatible APIs in the “production” ones). (And then when you fix any usage of APIs deprecated in 20.09, 21.01 upgrade in the future will be similar zero-cost). If you notice that the upgrade is painful for some reason, this will highlight the architectural issues/questions that need to be resolved. It’s much better to do it early and proactively. —a > On 17 Sep 2020, at 06:01, Mahdi Varasteh <mahdy.varas...@gmail.com> wrote: > > Hi Andrew, > > Thanks for you response. That makes sense. I will monitor my box memory usage. > Unfortunately I'm using VPP 20.05. So I will try to forwardport( we have it? > :D) this patch to it. > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17434): https://lists.fd.io/g/vpp-dev/message/17434 Mute This Topic: https://lists.fd.io/mt/76882936/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
