tree 073958fdc459566c31bf02177ada4f42ac1e3b03
parent d5bc1613d02f1c3f1226e2f7d555f0384d973482
author Eric Dumazet <edumazet@google.com> 1486660204 -0800
committer David S. Miller <davem@davemloft.net> 1487178378 -0500

mlx4: do not use rwlock in fast path

Using a reader-writer lock in fast path is silly, when we can
instead use RCU or a seqlock.

For mlx4 hwstamp clock, a seqlock is the way to go, removing
two atomic operations and false sharing.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Tariq Toukan <tariqt@mellanox.com>
Reviewed-by: Tariq Toukan <tariqt@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>