On 2/9/23 18:32, dheeraj wrote:
>
> Hi Ilya Maximets ,
>
> I have few more queries on your tests .
> What is the traffic rate ?
Maximum that OVS can handle. Basically, testpmd app generates
as many packets as OVS is able to receive. On my setup this
is about 8 Mpps.
> Please provide some
Hi Ilya Maximets ,
I have few more queries on your tests .
What is the traffic rate ?
Please provide some more details on traffic type . tcp or udp , packet size ,
traffic duration
Is OVS started with dpdk mode or kernel mode ?
How are you measuring the performance ?
Regards ,
Dheeraj
On 2/9/23 17:57, dheeraj wrote:
> Hi Ilya Maximets ,
>
> I did internal performance benchmarking tests with this patch . I tried with
> different traffic (udp and vxlan) and with different packet size (64 and
> 1024) . I don’t observe any performance degradation by applying the patch .
> Even
Hi Ilya Maximets ,
I did internal performance benchmarking tests with this patch . I tried with
different traffic (udp and vxlan) and with different packet size (64 and 1024)
. I don’t observe any performance degradation by applying the patch .
Even from the code changes , it doesn't look
On 1/13/23 13:20, Dheeraj Kumar wrote:
> Problem Statement:
> Before OVS 2.12 the OVS-DPDK datapath transmitted processed rx packet batches
> directly to the wanted tx queues. In OVS 2.12 each PMD stores the processed
> packets in an intermediate buffer per output port and flushes these output
>
Bleep bloop. Greetings dheeraj, I am a robot and I have tried out your patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
ERROR: Author dheeraj needs to sign off.
WARNING: Unexpected sign-offs from developers who are not
Problem Statement:
Before OVS 2.12 the OVS-DPDK datapath transmitted processed rx packet batches
directly to the wanted tx queues. In OVS 2.12 each PMD stores the processed
packets in an intermediate buffer per output port and flushes these output
buffers in a separate step. This buffering was
