[vpp-dev] VPP 20.09 RC1 milestone is complete!

2020-09-09 Thread Andrew Yourtchenko
Hi all, This is to let you know that stable/2009 branch has been created, and the RC1 artifacts are at packagecloud.io/fdio/2009. (Note: slight change of naming, it has “0” in the artifact name now.) Master branch is fully open for business. Stable/2009 branch is accepting the fixes in prepara

Re: [vpp-dev]: Crash in Timer wheel infra

2020-09-09 Thread Dave Barach via lists.fd.io
s/10us/100us/ seems to work as expected. Diffs under separate cover. Let me know what happens. HTH... D From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via lists.fd.io Sent: Wednesday, September 9, 2020 8:15 AM To: Rajith PR Cc: vpp-dev Subject: Re: [vpp-dev]: Crash in Timer wheel infra

Re: [vpp-dev]: Crash in Timer wheel infra

2020-09-09 Thread Dave Barach via lists.fd.io
“wheel slips” – aka calling tw_timer_expire_timer[_vec] later than expected every so often – is not a catastrophic problem; so long as the delay isn’t ridiculous. You’d need to compute mean delay and delay variance to know whether the slips that you’re seeing are trivial, or non-trivial. Conside

[vpp-dev] How to distinguish between l2-input-classify and l2-input-acl

2020-09-09 Thread yan mo
Hi Andrew, Thanks for your explanation. 发件人: Andrew 👽 Yourtchenko [mailto:ayour...@gmail.com] 发送时间: 2020年9月9日 17:51 收件人: yan mo 抄送: vpp-dev 主题: Re: [vpp-dev] How to distinguish between l2-input-classify and l2-input-acl Hi Yan, Historically the L2 and L3 packet path node graphs were very differ

Re: [vpp-dev] How to distinguish between l2-input-classify and l2-input-acl

2020-09-09 Thread Andrew Yourtchenko
Hi Yan, Historically the L2 and L3 packet path node graphs were very different, so the reason is probably just that - that you can’t have the fully unified processing in general. I spent some effort in ACL plugin creating the “works in all modes the same” abstraction layer, it is at least poss

答复: [vpp-dev] How to distinguish between l2-input-classify and l2-input-acl

2020-09-09 Thread yan mo
Hi Andrew, Thanks for the quick response. Your answer is helpful to me. In addition, I would like to ask another question, why ACL rules must be bound to the port mode, for example, when I configure as follows, the port host-vpp1 does not match the packet. Only when I configure the port to L2 m

Re: [vpp-dev] How to distinguish between l2-input-classify and l2-input-acl

2020-09-09 Thread Andrew Yourtchenko
L2-input classify is indeed a superset of l2-input-ACL, and allows some more functionality like setting the next node index based on the match. You would use ACL if you need the above “enhanced” functionality but also want to maintain the ability to apply policy. --a > On 9 Sep 2020, at 10:08,

[vpp-dev] How to distinguish between l2-input-classify and l2-input-acl

2020-09-09 Thread yan mo
Dear all, I have a question: what is the difference between l2-input-classify and l2-input-acl. They can all complete the ACL function, which one should I choose. I create a classify table and session follow this: classify table mask l2 dst classify session acl