>>
>> 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
>bot
Hi Pavan,
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
> >> b
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
>>
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 t
On Mon, Oct 14, 2019 at 11:52 PM wrote:
>
> From: Pavan Nikhilesh
>
> This patchset adds a new application to demonstrate the usage of event
> mode. The poll mode is also available to help with the transition.
>
> The following new command line parameters are added:
> --mode: Dictates the mode o
From: Pavan Nikhilesh
This patchset adds a new application to demonstrate the usage of event
mode. The poll mode is also available to help with the transition.
The following new command line parameters are added:
--mode: Dictates the mode of operation either poll or event.
--eventq_sched: Dict
6 matches
Mail list logo
