prakash
>Cc: Daniele Di Proietto ; Kavanagh, Mark B
>; dev@openvswitch.org
>Subject: Re: [ovs-dev] [PATCH v5] netdev-dpdk: Set pmd thread priority
>
>On Thu, Jul 28, 2016 at 03:39:58PM +, Bodireddy, Bhanuprakash wrote:
>> >-Original Message-
>> >From: Da
>-Original Message-
>From: Daniele Di Proietto [mailto:diproiet...@ovn.org]
>Sent: Wednesday, July 27, 2016 10:10 PM
>To: Kavanagh, Mark B
>Cc: Bodireddy, Bhanuprakash ;
>dev@openvswitch.org
>Subject: Re: [PATCH v5] netdev-dpdk: Set pmd thread priority
>
>Thanks for the patch, the implemen
On Thu, Jul 28, 2016 at 03:39:58PM +, Bodireddy, Bhanuprakash wrote:
> >-Original Message-
> >From: Daniele Di Proietto [mailto:diproiet...@ovn.org]
> >Sent: Wednesday, July 27, 2016 10:10 PM
> >To: Kavanagh, Mark B
> >Cc: Bodireddy, Bhanuprakash ;
> >dev@openvswitch.org
> >Subject: Re
>-Original Message-
>From: Daniele Di Proietto [mailto:diproiet...@ovn.org]
>Sent: Wednesday, July 27, 2016 10:10 PM
>To: Kavanagh, Mark B
>Cc: Bodireddy, Bhanuprakash ;
>dev@openvswitch.org
>Subject: Re: [PATCH v5] netdev-dpdk: Set pmd thread priority
>
>Thanks for the patch, the implemen
Thanks for the patch, the implementation looks good to me too.
During testing I kept noticing that it's way too easy to make OVS
completely unresponsive. As you point out in the documentation by having
dpdk-lcore-mask the same as pmd-cpu-mask, OVS cannot even be killed (a kill
-9 is required). I
>
>Set the DPDK pmd thread scheduling policy to SCHED_RR and static
>priority to highest priority value of the policy. This is to deal with
>pmd thread starvation case where another cpu hogging process can get
>scheduled/affinitized on to the same core the pmd thread is running
>there by significan
Set the DPDK pmd thread scheduling policy to SCHED_RR and static
priority to highest priority value of the policy. This is to deal with
pmd thread starvation case where another cpu hogging process can get
scheduled/affinitized on to the same core the pmd thread is running
there by significantly imp