On 7 May 2019, at 16:00, Ilya Maximets wrote:
On 07.05.2019 16:46, Eelco Chaudron wrote:
On 30 Apr 2019, at 14:17, David Marchand wrote:
pmd reloads are currently serialised in each steps calling
reload_affected_pmds.
Any pmd processing packets, waiting on a mutex etc... will make
other
On 07.05.2019 16:46, Eelco Chaudron wrote:
>
>
> On 30 Apr 2019, at 14:17, David Marchand wrote:
>
>> pmd reloads are currently serialised in each steps calling
>> reload_affected_pmds.
>> Any pmd processing packets, waiting on a mutex etc... will make other
>> pmd threads wait for a delay that
On 30 Apr 2019, at 14:17, David Marchand wrote:
pmd reloads are currently serialised in each steps calling
reload_affected_pmds.
Any pmd processing packets, waiting on a mutex etc... will make other
pmd threads wait for a delay that can be undeterministic when syscalls
adds up.
Switch to a
pmd reloads are currently serialised in each steps calling
reload_affected_pmds.
Any pmd processing packets, waiting on a mutex etc... will make other
pmd threads wait for a delay that can be undeterministic when syscalls
adds up.
Switch to a little busy loop on the control thread using an atomic
