diff options
| author | Eric Dumazet <edumazet@google.com> | 2017-02-09 20:10:04 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-02-15 20:06:18 +0300 |
| commit | 99f5711e7c15e997c4eb34b378502ef6f3982233 (patch) | |
| tree | 073958fdc459566c31bf02177ada4f42ac1e3b03 /include/linux/memory_hotplug.h | |
| parent | d5bc1613d02f1c3f1226e2f7d555f0384d973482 (diff) | |
| download | linux-99f5711e7c15e997c4eb34b378502ef6f3982233.tar.xz | |
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>
Diffstat (limited to 'include/linux/memory_hotplug.h')
0 files changed, 0 insertions, 0 deletions