Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload

Mon, Jul 29, 2019 at 02:47:07PM CEST, we...@ucloud.cn wrote: > >在 2019/7/29 19:13, Jiri Pirko 写道: >> Sun, Jul 28, 2019 at 08:52:47AM CEST, we...@ucloud.cn wrote: >>> From: wenxu >>> >>> move tc indirect block to flow_offload and rename >>> it to flow indirect block.The nf_tables can use the >>> in

Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload

在 2019/7/29 19:13, Jiri Pirko 写道: > Sun, Jul 28, 2019 at 08:52:47AM CEST, we...@ucloud.cn wrote: >> From: wenxu >> >> move tc indirect block to flow_offload and rename >> it to flow indirect block.The nf_tables can use the >> indr block architecture. >> >> Signed-off-by: wenxu >> --- >> v3: sub

Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload

Sun, Jul 28, 2019 at 08:52:47AM CEST, we...@ucloud.cn wrote: >From: wenxu > >move tc indirect block to flow_offload and rename A sentence should start with capital letter. >it to flow indirect block.The nf_tables can use the There should be a space between "." and first letter of the next sens

Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload

Sun, Jul 28, 2019 at 08:52:47AM CEST, we...@ucloud.cn wrote: >From: wenxu > >move tc indirect block to flow_offload and rename >it to flow indirect block.The nf_tables can use the >indr block architecture. > >Signed-off-by: wenxu >--- >v3: subsys_initcall for init_flow_indr_rhashtable >v4: no cha

[PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload

From: wenxu move tc indirect block to flow_offload and rename it to flow indirect block.The nf_tables can use the indr block architecture. Signed-off-by: wenxu --- v3: subsys_initcall for init_flow_indr_rhashtable v4: no change drivers/net/ethernet/mellanox/mlx5/core/en_rep.c | 10 +- .../