diff options
author | Wei Wang <weiwan@google.com> | 2017-10-14 01:08:07 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-10-16 23:08:30 +0300 |
commit | 0da4af00b2ed3dbe46788623a696c4169447eadc (patch) | |
tree | b4a6120d1c252e7e1c8df5316db753ed36e8d682 /fs/btrfs/tests/inode-tests.c | |
parent | 0e80193bd8c1d97654f1a2f45934e7372e9a512e (diff) | |
download | linux-0da4af00b2ed3dbe46788623a696c4169447eadc.tar.xz |
ipv6: only update __use and lastusetime once per jiffy at most
In order to not dirty the cacheline too often, we try to only update
dst->__use and dst->lastusetime at most once per jiffy.
As dst->lastusetime is only used by ipv6 garbage collector, it should
be good enough time resolution.
And __use is only used in ipv6_route_seq_show() to show how many times a
dst has been used. And as __use is not atomic_t right now, it does not
show the precise number of usage times anyway. So we think it should be
OK to only update it at most once per jiffy.
According to my latest syn flood test on a machine with intel Xeon 6th
gen processor and 2 10G mlx nics bonded together, each with 8 rx queues
on 2 NUMA nodes:
With this patch, the packet process rate increases from ~3.49Mpps to
~3.75Mpps with a 7% increase rate.
Note: dst_use() is being renamed to dst_hold_and_use() to better specify
the purpose of the function.
Signed-off-by: Wei Wang <weiwan@google.com>
Acked-by: Eric Dumazet <edumazet@googl.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/btrfs/tests/inode-tests.c')
0 files changed, 0 insertions, 0 deletions