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 collector, it should
> be good enough time
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 try to only update
> >> dst->__use
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.
>
>
> > As dst->last
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 jiffy.
>
>
>> As dst->lastusetime i
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 should
> be good enough
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 ipv6_route_seq_show() to show
