Re: [ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and queues handling code.

2016-11-23 Thread Bodireddy, Bhanuprakash
>-Original Message- >From: Daniele Di Proietto [mailto:diproiet...@ovn.org] >Sent: Tuesday, November 22, 2016 9:01 PM >To: Bodireddy, Bhanuprakash >Cc: d...@openvswitch.org >Subject: Re: [ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and >queues handling co

Re: [ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and queues handling code.

2016-11-22 Thread Daniele Di Proietto
vember 16, 2016 12:46 AM > >To: d...@openvswitch.org > >Cc: Daniele Di Proietto > >Subject: [ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and > >queues handling code. > > > >Currently we have three different code paths that deal with pmd threads > and

Re: [ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and queues handling code.

2016-11-22 Thread Bodireddy, Bhanuprakash
>-Original Message- >From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- >boun...@openvswitch.org] On Behalf Of Daniele Di Proietto >Sent: Wednesday, November 16, 2016 12:46 AM >To: d...@openvswitch.org >Cc: Daniele Di Proietto >Subject: [ovs-dev] [PAT

[ovs-dev] [PATCH 16/17] dpif-netdev: Centralized threads and queues handling code.

2016-11-15 Thread Daniele Di Proietto
Currently we have three different code paths that deal with pmd threads and queues, in response to different input 1. When a port is added 2. When a port is deleted 3. When the cpumask changes or a port must be reconfigured. 1. and 2. are carefully written to minimize disruption to the running da