On 3/21/2018 8:09 PM, Yishai Hadas wrote:
This series from Matan adds ESP flow action support, the matching kernel series
was already sent to rdma-next.
Currently, when adding a flow steering rule, actions such as TAG or DROP could
be specified in the flow action specification. However, some flow actions
could be complex and needs to be shared between several flow steering rules.
Therefore, we add a new flow actions mechanism. Flow actions are actions the
user creates and are given as handles for the flow steering rules.
We start with adding the ESP flow action, which supports both full offload and
inline crypto mode. We currently only support AES_GCM crypto with bitmap
replay protection. These new create, modify and destroy flow_action_esp
methods are implemented using the new uverbs ioctl() infrastructure.
Furthermore, the current mlx5 device works in a different way from future
devices. Thus, when creating the flow action, the user has to use the mlx5dv
API to specify specific driver's flags.
ESP flow action is supported for both egress and ingress. Therefore, we also
add a flag for egress steering in our flow steering implementation. Egress
steering is currently only implemented for ESP flows. In order to carry these
actions only for ESP packets, we also add an ESP match filter. Finally, we also
add the required bits to support RSS for ESP flows and query the feature's
support.
PR was sent:
https://github.com/linux-rdma/rdma-core/pull/311
The PR was updated as of below:
- As of Travis note:
Add to 'non_cxx_headers' in buildlib/check-build few header files that
should be ignored.
- Fix rebase issue, no code change in final series:
Use as part of patch #2 DECLARE_COMMAND_BUFFER_LINK instead of
DECLARE_COMMAND_BUFFER which was changed in patch #5 to the expected code.
Current note from Travis is some false alarm around the checkpatch of MD
files and macro usage.
Yishai
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
