Re: [PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-16 Thread David Miller
From: Wei Wang Date: Fri, 13 Oct 2017 15:08:07 -0700 > From: Wei Wang > > 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

Re: [PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-15 Thread Martin KaFai Lau
On Sat, Oct 14, 2017 at 12:26:28AM +, Eric Dumazet wrote: > On Fri, Oct 13, 2017 at 5:09 PM, Martin KaFai Lau wrote: > > On Fri, Oct 13, 2017 at 10:08:07PM +, Wei Wang wrote: > >> From: Wei Wang > >> > >> In order to not dirty the cacheline too often, we

Re: [PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-15 Thread Paolo Abeni
On Fri, 2017-10-13 at 17:09 -0700, Martin KaFai Lau wrote: > On Fri, Oct 13, 2017 at 10:08:07PM +, Wei Wang wrote: > > From: Wei Wang > > > > In order to not dirty the cacheline too often, we try to only update > > dst->__use and dst->lastusetime at most once per jiffy. >

Re: [PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-13 Thread Eric Dumazet
On Fri, Oct 13, 2017 at 5:09 PM, Martin KaFai Lau wrote: > On Fri, Oct 13, 2017 at 10:08:07PM +, Wei Wang wrote: >> From: Wei Wang >> >> In order to not dirty the cacheline too often, we try to only update >> dst->__use and dst->lastusetime at most once per

Re: [PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-13 Thread Martin KaFai Lau
On Fri, Oct 13, 2017 at 10:08:07PM +, Wei Wang wrote: > From: Wei Wang > > 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

[PATCH net-next] ipv6: only update __use and lastusetime once per jiffy at most

2017-10-13 Thread Wei Wang
From: Wei Wang 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