Re: [ovs-dev] [PATCH] packets: Do not initialize ct_orig_tuple.

2017-07-12 Thread Bodireddy, Bhanuprakash
@intel.com>; >d...@openvswitch.org >Subject: Re: [ovs-dev] [PATCH] packets: Do not initialize ct_orig_tuple. > >I tested and found similar ballpark performance increase (approx. 10%) in the >most simple case with decreasing benefit as the pipeline gets more realistic >and useful. > >This

Re: [ovs-dev] [PATCH] packets: Do not initialize ct_orig_tuple.

2017-07-09 Thread Darrell Ball
I tested and found similar ballpark performance increase (approx. 10%) in the most simple case with decreasing benefit as the pipeline gets more realistic and useful. This ideal case incremental beyond the original fix patch (from Daniele) shows a small decrease in performance of approx 100k

Re: [ovs-dev] [PATCH] packets: Do not initialize ct_orig_tuple.

2017-06-23 Thread Stokes, Ian
> -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Bhanuprakash Bodireddy > Sent: Thursday, June 22, 2017 10:09 PM > To: d...@openvswitch.org > Subject: [ovs-dev] [PATCH] packets: Do not initia

[ovs-dev] [PATCH] packets: Do not initialize ct_orig_tuple.

2017-06-22 Thread Bhanuprakash Bodireddy
Commit "odp: Support conntrack orig tuple key." introduced new fields in struct 'pkt_metadata'. pkt_metadata_init() is called for every packet in the userspace datapath. When testing a simple single flow case with DPDK, we observe a lower throughput after the above commit (it was 14.88 Mpps