[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211006173841.63dde6f6@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 6 Oct 2021 17:38:41 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Volodymyr Mytnyk <volodymyr.mytnyk@...ision.eu>
Cc: netdev@...r.kernel.org, Volodymyr Mytnyk <vmytnyk@...vell.com>,
"David S. Miller" <davem@...emloft.net>, Chris Mi <cmi@...dia.com>,
Roi Dayan <roid@...dia.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] flow_offload: add l4 port range match
On Wed, 6 Oct 2021 16:06:54 +0300 Volodymyr Mytnyk wrote:
> From: Volodymyr Mytnyk <vmytnyk@...vell.com>
>
> Current flow offload API doen't allow to offload l4 port range
> match dissector (FLOW_DISSECTOR_KEY_PORTS_RANGE) in the driver,
> as is no relevant data struct that will hold this information
> and pass it to the driver.
>
> Thus, to make offload of l4 port range possible by other drivers
> add dedicated dissector port range struct to get min and max
> value provided by user.
>
> - add flow_dissector_key_ports_range to store
> l4 port range match.
> - add flow_match_ports_range key/mask
>
> tc cmd example:
> tc qd add dev PORT clsact
> tc filter add dev PORT protocol ip ingress \
> flower skip_sw ip_proto udp src_port 2-37 action drop
>
> Signed-off-by: Volodymyr Mytnyk <vmytnyk@...vell.com>
A driver implementation needs to be posted in the same series.
Otherwise it's an API with no in-tree user. Let's consider this
posting an RFC.
Powered by blists - more mailing lists