From: wenxu <wenxu@ucloud.cn>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v3 0/4] netfilter: nf_tables_offload: clean offload things when the device unregister
Date: Fri, 6 Sep 2019 11:09:46 +0800 [thread overview]
Message-ID: <b2a6f0fb-1155-2384-c880-a7d9ce08bc4f@ucloud.cn> (raw)
In-Reply-To: <20190906002754.34ge3qjx3qtu7ao5@salvia>
On 9/6/2019 8:27 AM, Pablo Neira Ayuso wrote:
> On Thu, Sep 05, 2019 at 12:00:15PM +0800, wenxu@ucloud.cn wrote:
>> From: wenxu <wenxu@ucloud.cn>
>>
>> This series clean the offload things for both chain and rules when the
>> related device unregister
>>
>> This version add a nft_offload_netdev_iterate common function
>>
>> wenxu (4):
>> netfilter: nf_tables_offload: refactor the nft_flow_offload_chain
>> function
>> netfilter: nf_tables_offload: refactor the nft_flow_offload_rule
>> function
> 1/4 and 2/4 are not required anymore after adding the registration
> logic to nf_tables_offload.
Maybe it also need the 1/4 and 2/4 patches. The nft_flow_offload_chain/rule need
get some inform from the nft_trans. There is no this struct in the netdev notify event,.
So it better to refactor it more common?
>
prev parent reply other threads:[~2019-09-06 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 4:00 [PATCH nf-next v3 0/4] netfilter: nf_tables_offload: clean offload things when the device unregister wenxu
2019-09-05 4:00 ` [PATCH nf-next v3 1/4] netfilter: nf_tables_offload: refactor the nft_flow_offload_chain function wenxu
2019-09-05 4:00 ` [PATCH nf-next v3 2/4] netfilter: nf_tables_offload: refactor the nft_flow_offload_rule function wenxu
2019-09-05 4:00 ` [PATCH nf-next v3 3/4] netfilter: nf_tables_offload: add nft_offload_netdev_iterate function wenxu
2019-09-06 0:34 ` Pablo Neira Ayuso
2019-09-06 3:25 ` wenxu
2019-09-05 4:00 ` [PATCH nf-next v3 4/4] netfilter: nf_tables_offload: clean offload things when the device unregister wenxu
2019-09-06 0:27 ` [PATCH nf-next v3 0/4] " Pablo Neira Ayuso
2019-09-06 3:09 ` wenxu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2a6f0fb-1155-2384-c880-a7d9ce08bc4f@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).