Hi Daniel, ODP support for IPsec was introduced in v1.17.0.0 and is part of the Tiger Moth LTS level of the code (v1.19 series). If your intent is to do things with IPsec I recommend upgrading to that. The current LTS support level is v1.19.0.1. I'm not sure if that will work with MACSAD, but you might want to check.
Are you able to see if this level of the code works for you? Thanks. On Mon, Jun 18, 2018 at 2:33 PM, Maxim Uvarov <maxim.uva...@linaro.org> wrote: > how match do you pull head? Does this value fit into default headroom? > > Maxim. > > On 18 June 2018 at 18:34, Daniel Feferman <dlfefer...@gmail.com> wrote: > >> Hi Bill, >> >> Thank you for your answer. Answering your questions: >> >> -v16. odp-linux. >> -It was a Xeon E5, then x86 using a link of up to 10G. >> -I'm new on ODP, I'm currently working on a VXLAN implementation (but we >> similar problem with a BNG use case) using P4 language with this compiler >> (which I'm a bit more familiar) that uses ODP: >> https://github.com/intrig-unicamp/macsad >> >> So, you may be right, it may be after APIs are called. However, for now, >> my >> best guess was something known with ODP. I was thinking to run one of ODP >> examples with both functions to test the performance and see if I get the >> same throughput to discard ODP. I saw this IPsec which seems to use both >> of >> them, but I'm sending packets and it's not forwarding, I've tried the >> "--enable-debug-print" flag but I was not able to figure it out what's >> wrong. >> >> I'm running IPsec using: >> >> ./odp_ipsec -i veth1,veth3,veth5 -m 0 >> >> I'm using scapy to send the packet set like: >> >> pkt1 = >> Ether(dst='08:00:27:4C:55:CC',src='08:00:27:76:B5:E0')/IP(ds >> t='192.168.111.1',src='192.168.111.2') >> >> And sending it through veth1. Am I doing something wrong? Do you have any >> hint about it? >> >> Best, >> Daniel >> >> >> On Mon, Jun 18, 2018 at 11:54 AM Bill Fischofer < >> bill.fischo...@linaro.org> >> wrote: >> >> > Hi Daniel. Can you give a bit more detail? >> > >> > - What version of ODP are you using? Is this the odp-linux or odp-dpdk >> > reference implementations from GitHub or some other implementation? >> > - The platform / system you're running on. x86? Arm? Something else? >> > - A small code snippet / test program illustrating what you're trying to >> > do? >> > >> > The push/pull routines should have similar performance characteristics. >> > The differences you're observing may be due to what's happening in your >> > program after these APIs are called. >> > >> > On Mon, Jun 18, 2018 at 9:35 AM, Daniel Feferman <dlfefer...@gmail.com> >> > wrote: >> > >> >> Hi all, >> >> >> >> I'm running a compiler that takes advantage of ODP to allow good >> >> throughput >> >> with portability. However, one of our tests seems to point that >> >> odp_packet_pull_head >> >> strongly impact the performance compared to the "opposite" function ( >> >> odp_packet_push_head), I mean a program using push seems have >> considerably >> >> better throughput than the same using pull. Is it a known issue or >> >> something that someone has seen before? >> >> >> >> Furthermore, I'm trying to run IPsec example to test it, but I was not >> >> able >> >> to run it with 3 different veth interface, ODP simply does not forward >> the >> >> packet. Do I really need 3 separate VMs to run it or may I use veth to >> set >> >> similar environment? >> >> >> >> Thanks, >> >> Daniel >> >> >> > >> > >> > >
