On 24/03/2016 09:18, "Ben Pfaff" wrote:
>On Wed, Mar 23, 2016 at 06:02:58PM -0700, Daniele Di Proietto wrote:
>> A new thread must be started in a non quiescent state. There is a call
>> to ovsrcu_quiesce_end() in ovsthread_wrapper(), to enforce this.
>>
>> ovs_thread_create(), instead, is ex
On Wed, Mar 23, 2016 at 06:02:58PM -0700, Daniele Di Proietto wrote:
> A new thread must be started in a non quiescent state. There is a call
> to ovsrcu_quiesce_end() in ovsthread_wrapper(), to enforce this.
>
> ovs_thread_create(), instead, is executed in the parent thread, and
> calling ovsrcu
Oops, I forgot my signoff. Here it is:
Signed-off-by: Daniele Di Proietto
On 23/03/2016 18:02, "Daniele Di Proietto" wrote:
>A new thread must be started in a non quiescent state. There is a call
>to ovsrcu_quiesce_end() in ovsthread_wrapper(), to enforce this.
>
>ovs_thread_create(), instea
A new thread must be started in a non quiescent state. There is a call
to ovsrcu_quiesce_end() in ovsthread_wrapper(), to enforce this.
ovs_thread_create(), instead, is executed in the parent thread, and
calling ovsrcu_quiesce_end() there will cause the parent to end its
(possible) quiescing stat
