On Mon, Jun 05, 2023 at 03:39:02PM +0200, Eelco Chaudron wrote: > Make the read of the current seq->value atomic, i.e., not needing to > acquire the global mutex when reading it. On 64-bit systems, this > incurs no overhead, and it will avoid the mutex and potentially > a system call. > > For incrementing the value followed by waking up the threads, we are > still taking the mutex, so the current behavior is not changing. The > seq_read() behavior is already defined as, "Returns seq's current > sequence number (which could change immediately)". So the change > should not impact the current behavior. > > Signed-off-by: Eelco Chaudron <[email protected]>
Reviewed-by: Simon Horman <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
