Re: [dpdk-dev] [PATCH v6 00/10] example/l2fwd-event: introduce l2fwd-event example

[Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>]

Hi Vipin,

>Hi Pavan,
>
>Thanks for sharing the write up, following are some of my thoughts.
>
>Snipped
>>
>> Based on event device capability the configuration is done as follows:
>>     - A single event device is enabled.
>>     - The number of event ports is equal to the number of worker
>>       cores enabled in the core mask. Additional event ports might
>>       be configured based on Rx/Tx adapter capability.
>>     - The number of event queues is equal to the number of ethernet
>>       ports. If Tx adapter doesn't have internal port capability then
>>       an additional single link event queue is used to enqueue events
>>       to Tx adapter.
>1. Are we support per port function as 'mac_updating' and
>'non_macupdating'?
No, its global.

>2. If no for above, why is that each port should have ` number of event
>queues is equal to the number of ethernet`?

It's not a quantifier of each port, It across the eventdevice that the number 
of event queues is equal to number of ethdevices used.

This is to prevent event queues being overcrowded i.e. in case there is only 
one event queue and multiple Eth devices then SW/HW will have a bottleneck
in enqueueing all the mbufs to a single event queue. 

>3. With this work for vdev ports, if no are we adding check for the same
>in `main` function?

I have verified the functionality for --vdev=event_sw0 and it seems to work fine.

>
>snipped