Re: [ovs-dev] [PATCH v2] dpif-netdev: proper tx queue id

2015-08-18 Thread Ilya Maximets
Thanks for review. I sent new version of patch. http://openvswitch.org/pipermail/dev/2015-August/058926.html Best regards, Ilya Maximets. On 17.08.2015 19:45, Daniele Di Proietto wrote: > Sorry about the long wait. > > I think this is the right direction, I like the idea of having a thread > lo

Re: [ovs-dev] [PATCH v2] dpif-netdev: proper tx queue id

2015-08-17 Thread Daniele Di Proietto
Sorry about the long wait. I think this is the right direction, I like the idea of having a thread local map of the txqs. It will allow us to assign the txqs in a more sophisticated way. I see some unit tests failing with this patch applied. Could you try running the testsuite with 'make check'

Re: [ovs-dev] [PATCH v2] dpif-netdev: proper tx queue id

2015-08-13 Thread Ilya Maximets
ping. On 06.08.2015 17:32, Ilya Maximets wrote: > Currently tx_qid is equal to pmd->core_id. This leads to unexpected > behavior if pmd-cpu-mask different from '/(0*)(1|3|7)?(f*)/', > e.g. if core_ids are not sequential, or doesn't start from 0, or both. > > Example: > starting 2 pmd thread

[ovs-dev] [PATCH v2] dpif-netdev: proper tx queue id

2015-08-06 Thread Ilya Maximets
Currently tx_qid is equal to pmd->core_id. This leads to unexpected behavior if pmd-cpu-mask different from '/(0*)(1|3|7)?(f*)/', e.g. if core_ids are not sequential, or doesn't start from 0, or both. Example: starting 2 pmd threads with 1 port, 2 rxqs per port, pmd-cpu-mask =