Re: [ovs-dev] [PATCH v7 4/5] conntrack: Use an atomic conn expiration value

2022-07-11 Thread Aaron Conole
Paolo Valerio writes: > From: Gaetan Rivet > > A lock is taken during conn_lookup() to check whether a connection is > expired before returning it. This lock can have some contention. > > Even though this lock ensures a consistent sequence of writes, it does > not imply a specific order. A

Re: [ovs-dev] [PATCH v7 4/5] conntrack: Use an atomic conn expiration value

2022-07-11 Thread 0-day Robot
Bleep bloop. Greetings Paolo Valerio, I am a robot and I have tried out your patch. Thanks for your contribution. I encountered some error that I wasn't expecting. See the details below. checkpatch: WARNING: Unexpected sign-offs from developers who are not authors or co-authors or

[ovs-dev] [PATCH v7 4/5] conntrack: Use an atomic conn expiration value

2022-07-11 Thread Paolo Valerio
From: Gaetan Rivet A lock is taken during conn_lookup() to check whether a connection is expired before returning it. This lock can have some contention. Even though this lock ensures a consistent sequence of writes, it does not imply a specific order. A ct_clean thread taking the lock first