From: <[email protected]> on behalf of Darrell Ball <[email protected]> Date: Sunday, June 11, 2017 at 10:55 AM To: Hui Xiang <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [ovs-discuss] OVS-DPDK polling cycles and processing cycles for pmd
From: <[email protected]> on behalf of Hui Xiang <[email protected]> Date: Saturday, June 10, 2017 at 9:06 PM To: "[email protected]" <[email protected]> Subject: [ovs-discuss] OVS-DPDK polling cycles and processing cycles for pmd Hi guys, I got below results on my environment, but confusing with the cycles percents, it looks like the polling plus processing cycles per pmd is 100%, but as I recalled there are some improvment document that showed their processing cycles are 100% percents which means 0 for polling cycles? how should be the rate of polling and processing cycles take? should it be better for less polling and much processing for performance's benefits? “polling” is checking for packets, but there are none to process. Above will be the definition when https://patchwork.ozlabs.org/patch/729970/ is pushed. In the software that you are using, “polling” is the time spent polling when there are no packets and also polling/receiving/batching packets. Using this definition, polling percentage will not go below “some value”, since even if all polling cycles receive packets that time spent polling/receiving/batching is counted as “polling”. input more packets -> higher “processing” percentage. pmd thread numa_id 1 core_id 27: emc hits:141332792126 megaflow hits:263 avg. subtable lookups per hit:1.00 miss:59 lost:0 polling cycles:19832152639760 (12.60%) processing cycles:137517517407771 (87.40%) avg cycles per packet: 1113.33 (157349670047531/141332792711) avg processing cycles per packet: 973.01 (137517517407771/141332792711) Thanks a lot. BR.
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
