[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpWXgncANS5MrBzrZiEVSbGzNptrAjisg_K2NTA-PsAMKg@mail.gmail.com>
Date: Wed, 18 May 2016 10:17:24 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: David Miller <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Daniel Borkmann <daniel@...earbox.net>, nbd@....name,
baronchon@...m.org, Alexander Duyck <alexander.duyck@...il.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Eric Dumazet <eric.dumazet@...il.com>,
Jiří Pírko <jiri@...nulli.us>,
Alexei Starovoitov <alexei.starovoitov@...il.com>
Subject: Re: [net-next RFC 1/1] net sched actions: introduce timestamp for
first time used
On Tue, May 17, 2016 at 4:38 PM, Jamal Hadi Salim <jhs@...atatu.com> wrote:
> diff --git a/net/sched/act_bpf.c b/net/sched/act_bpf.c
> index 014f9a6..f581e01 100644
> --- a/net/sched/act_bpf.c
> +++ b/net/sched/act_bpf.c
> @@ -156,6 +156,7 @@ static int tcf_bpf_dump(struct sk_buff *skb, struct tc_action *act,
>
> tm.install = jiffies_to_clock_t(jiffies - prog->tcf_tm.install);
> tm.lastuse = jiffies_to_clock_t(jiffies - prog->tcf_tm.lastuse);
> + tm.firstuse = jiffies_to_clock_t(jiffies - prog->tcf_tm.firstuse);
> tm.expires = jiffies_to_clock_t(prog->tcf_tm.expires);
I think it is the time to add a wrapper for these tm.XX =
jiffies_to_clock_t(XXX).
Powered by blists - more mailing lists