From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1767FC31E40 for ; Sat, 3 Aug 2019 13:42:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DF46F2073D for ; Sat, 3 Aug 2019 13:42:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727556AbfHCNm2 (ORCPT ); Sat, 3 Aug 2019 09:42:28 -0400 Received: from m9784.mail.qiye.163.com ([220.181.97.84]:14178 "EHLO m9784.mail.qiye.163.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727529AbfHCNm2 (ORCPT ); Sat, 3 Aug 2019 09:42:28 -0400 Received: from [192.168.1.4] (unknown [222.68.27.146]) by m9784.mail.qiye.163.com (Hmail) with ESMTPA id 57A30415DE; Sat, 3 Aug 2019 21:42:21 +0800 (CST) Subject: Re: [PATCH net-next v5 5/6] flow_offload: support get flow_block immediately To: Jakub Kicinski Cc: jiri@resnulli.us, pablo@netfilter.org, fw@strlen.de, netfilter-devel@vger.kernel.org, netdev@vger.kernel.org, John Hurley References: <1564628627-10021-1-git-send-email-wenxu@ucloud.cn> <1564628627-10021-6-git-send-email-wenxu@ucloud.cn> <20190801161129.25fee619@cakuba.netronome.com> <55850b13-991f-97bd-b452-efacd0f39aa4@ucloud.cn> <20190802110216.5e1fd938@cakuba.netronome.com> <45660f1e-b6a8-1bcb-0d57-7c1790d3fbaf@ucloud.cn> <20190802172155.7a36713d@cakuba.netronome.com> From: wenxu Message-ID: <57c751f3-4b8e-7eb9-2ae0-1d72ca2c35e2@ucloud.cn> Date: Sat, 3 Aug 2019 21:42:06 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190802172155.7a36713d@cakuba.netronome.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZVkpVQ01NS0tLSUJPTUNOSE1ZV1koWU FJQjdXWS1ZQUlXWQkOFx4IWUFZNTQpNjo3JCkuNz5ZBg++ X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6MUk6LDo6LDg8Lk4BEhw9EAs1 HgIaCi5VSlVKTk1PQ0hCTE9KTU1DVTMWGhIXVQweFQMOOw4YFxQOH1UYFUVZV1kSC1lBWUlJSVVN Q1VJTFVKT01ZV1kIAVlBSU1JQjcG X-HM-Tid: 0a6c57b788ac2086kuqy57a30415de Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 在 2019/8/3 8:21, Jakub Kicinski 写道: > On Sat, 3 Aug 2019 07:19:31 +0800, wenxu wrote: >>> Or: >>> >>> device unregister: >>> - nft block destroy >>> - UNBIND cb >>> - free driver's block state >>> - driver notifier callback >>> - free driver's state >>> >>> No? >> For the second case maybe can't unbind cb? because the nft block is >> destroied. There is no way to find the block(chain) in nft. > But before the block is destroyed doesn't nft send an UNBIND event to > the drivers, always? you are correct, it will be send an UBIND event when the block is destroyed