From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next v10 1/3] act_vlan: Change stats update to use
 per-core stats
Date: Thu, 09 Nov 2017 08:42:40 +0900 (KST)
Message-ID: <20171109.084240.936752820428817969.davem@davemloft.net>
References: <CAJ3xEMhuhAjn5TdoOxSLXmsGbEbhP1QJ4up63NiUgN_JEU8Jmw@mail.gmail.com>
        <CAJrKpLYJRqtMbiA7w8i3d+BUEtHMkoB649=N-aAHXd1vjboCGw@mail.gmail.com>
        <CAJ3xEMieRd+4UOD1zxoiO-ovR=URBARQb--WdDxy54RuLF2Y7Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: kurup.manish@gmail.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
        jiri@resnulli.us, jakub.kicinski@netronome.com,
        pieter.jansenvanvuuren@netronome.com, simon.horman@netronome.com,
        john.hurley@netronome.com, oss-drivers@netronome.com,
        netdev@vger.kernel.org, aring@mojatatu.com, mrv@mojatatu.com,
        manish.kurup@verizon.com
To: gerlitz.or@gmail.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:52532 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752741AbdKHXm4 (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 8 Nov 2017 18:42:56 -0500
In-Reply-To: <CAJ3xEMieRd+4UOD1zxoiO-ovR=URBARQb--WdDxy54RuLF2Y7Q@mail.gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Or Gerlitz <gerlitz.or@gmail.com>
Date: Thu, 9 Nov 2017 06:40:06 +0900

> On Thu, Nov 9, 2017 at 12:45 AM, Manish Kurup <kurup.manish@gmail.com> wrote:
>> On Wed, Nov 8, 2017 at 9:20 AM, Or Gerlitz <gerlitz.or@gmail.com> wrote:
>>> On Wed, Nov 8, 2017 at 9:03 PM, Manish Kurup <kurup.manish@gmail.com> wrote:
> 
>>>> @@ -30,9 +30,10 @@ static int tcf_vlan(struct sk_buff *skb, const struct tc_action *a,
>>>>         int err;
>>>>         u16 tci;
>>>>
>>>> -       spin_lock(&v->tcf_lock);
>>>>         tcf_lastuse_update(&v->tcf_tm);
>>>> -       bstats_update(&v->tcf_bstats, skb);
>>>> +       bstats_cpu_update(this_cpu_ptr(v->common.cpu_bstats), skb);
>>>> +
>>>> +       spin_lock(&v->tcf_lock);
>>>>         action = v->tcf_action;
>>>
> 
>>> before your changes the spin lock also protected the lastuse update call but
>>> now it doesn't, why?
> 
>> Phase I of my changes, was to get rid of spin_locks, and convert the
>> stats to a per-cpu stats model to get better forwarding performance.
>> While doing this, I looked at a few 'model TC actions' within
>> net/sched (tcf_mirred for example). Neither of them protected the
>> tcf_lastuse_update(). I assumed that this was the case because this
>> was a 'display-only' field, and as long as it changed to a latest
>> timestamp based on packets received, it was OK.
> 
> this is really late in the review cycle so lets not stop for that but
> if for some  reason there's V11 - would be good to put a comment on
> that in the change log

I think the async update of this lastuse value should be fine.