Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-29 Thread wenxu
在 2019/7/30 0:55, Jakub Kicinski 写道: > On Mon, 29 Jul 2019 15:18:03 +0800, wenxu wrote: >> On 7/29/2019 12:42 PM, Jakub Kicinski wrote: >>> On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: On 7/29/2019 4:16 AM, Jakub Kicinski wrote: > I don't know the nft code, but it seems unlikely

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-29 Thread Jakub Kicinski
On Mon, 29 Jul 2019 15:18:03 +0800, wenxu wrote: > On 7/29/2019 12:42 PM, Jakub Kicinski wrote: > > On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: > >> On 7/29/2019 4:16 AM, Jakub Kicinski wrote: > >>> I don't know the nft code, but it seems unlikely it wouldn't have the > >>> same problem/ne

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-29 Thread Jakub Kicinski
On Mon, 29 Jul 2019 15:05:34 +0800, wenxu wrote: > On 7/29/2019 12:42 PM, Jakub Kicinski wrote: > > On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: > >> On 7/29/2019 4:16 AM, Jakub Kicinski wrote: > >>> I don't know the nft code, but it seems unlikely it wouldn't have the > >>> same problem/ne

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-29 Thread wenxu
On 7/29/2019 12:42 PM, Jakub Kicinski wrote: > On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: >> On 7/29/2019 4:16 AM, Jakub Kicinski wrote: >>> I don't know the nft code, but it seems unlikely it wouldn't have the >>> same problem/need.. >> nft don't have the same problem.  The offload rule

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-29 Thread wenxu
On 7/29/2019 12:42 PM, Jakub Kicinski wrote: > On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: >> On 7/29/2019 4:16 AM, Jakub Kicinski wrote: >>> I don't know the nft code, but it seems unlikely it wouldn't have the >>> same problem/need.. >> nft don't have the same problem.  The offload rule

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-28 Thread Jakub Kicinski
On Mon, 29 Jul 2019 10:43:56 +0800, wenxu wrote: > On 7/29/2019 4:16 AM, Jakub Kicinski wrote: > > I don't know the nft code, but it seems unlikely it wouldn't have the > > same problem/need.. > > nft don't have the same problem.  The offload rule can only attached > to offload base chain. > >

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-28 Thread wenxu
On 7/29/2019 4:16 AM, Jakub Kicinski wrote: > . > The TC default block is there because the indirect registration may > happen _after_ the block is installed and populated. It's the device > driver that usually does the indirect registration, the tunnel device > and its rules may already be set

Re: [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-28 Thread Jakub Kicinski
On Sun, 28 Jul 2019 14:52:48 +0800, we...@ucloud.cn wrote: > From: wenxu > > When thre indr device register, it can get the default block > from tc immediately if the block is exist. > > Signed-off-by: wenxu > --- > v3: no change > v4: get tc default block without callback Please stop repostin

[PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately

2019-07-27 Thread wenxu
From: wenxu When thre indr device register, it can get the default block from tc immediately if the block is exist. Signed-off-by: wenxu --- v3: no change v4: get tc default block without callback include/net/pkt_cls.h | 7 +++ net/core/flow_offload.c | 2 ++ net/sched/cls_api.c |