[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <vbfh8ivm8b8.fsf@reg-r-vrt-018-180.mtr.labs.mlnx>
Date:   Wed, 12 Sep 2018 11:25:15 +0300
From:   Vlad Buslov <vladbu@...lanox.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        Jamal Hadi Salim <jhs@...atatu.com>,
        Jiri Pirko <jiri@...nulli.us>,
        David Miller <davem@...emloft.net>,
        Stephen Hemminger <stephen@...workplumber.org>,
        Kirill Tkhai <ktkhai@...tuozzo.com>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Nicolas Dichtel <nicolas.dichtel@...nd.com>,
        Leon Romanovsky <leon@...nel.org>,
        Greg KH <gregkh@...uxfoundation.org>, mark.rutland@....com,
        Florian Westphal <fw@...len.de>,
        David Ahern <dsahern@...il.com>,
        lucien xin <lucien.xin@...il.com>,
        Jakub Kicinski <jakub.kicinski@...ronome.com>,
        Christian Brauner <christian.brauner@...ntu.com>,
        Jiri Benc <jbenc@...hat.com>
Subject: Re: [PATCH net-next 09/13] net: sched: extend tcf_block with rcu
On Fri 07 Sep 2018 at 19:52, Cong Wang <xiyou.wangcong@...il.com> wrote:
> On Thu, Sep 6, 2018 at 12:59 AM Vlad Buslov <vladbu@...lanox.com> wrote:
>>
>> Extend tcf_block with rcu to allow safe deallocation when it is accessed
>> concurrently.
>
> This sucks, please fold this patch into where you call rcu_read_lock()
> on tcf block.
>
> This patch _alone_ is apparently not complete. This is not how
> we split patches.
Got it.
Powered by blists - more mailing lists
 
