kernel/linux.git/include/linux/mlx5/fs.h, branch v6.1.168Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v6.1.1682022-09-07T13:02:08+00:00net/mlx5: Add MACsec Rx tables support to fs_core2022-09-07T13:02:08+00:00Lior Nahmansonliorna@nvidia.com2022-09-06T05:21:24+00:00urn:sha1:15d187e285b3d5f4fe0328c09566355c1e387ff6
Add new namespace for MACsec RX flows.
Encrypted MACsec packets should be first decrypted and stripped
from MACsec header and then continues with the kernel's steering
pipeline.
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/mlx5: Add MACsec Tx tables support to fs_core2022-09-07T13:02:08+00:00Lior Nahmansonliorna@nvidia.com2022-09-06T05:21:20+00:00urn:sha1:ee534d7f81ba9cec028580f91429b3dc29b90c7f
Changed EGRESS_KERNEL namespace to EGRESS_IPSEC and add new
namespace for MACsec TX.
This namespace should be the last namespace for transmitted packets.
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/mlx5: Generalize Flow Context for new crypto fields2022-09-07T13:02:08+00:00Lior Nahmansonliorna@nvidia.com2022-09-06T05:21:17+00:00urn:sha1:e227ee990bf974f655ec3132b496409990f6634b
In order to support MACsec offload (and maybe some other crypto features
in the future), generalize flow action parameters / defines to be used by
crypto offlaods other than IPsec.
The following changes made:
ipsec_obj_id field at flow action context was changed to crypto_obj_id,
intreduced a new crypto_type field where IPsec is the default zero type
for backward compatibility.
Action ipsec_decrypt was changed to crypto_decrypt.
Action ipsec_encrypt was changed to crypto_encrypt.
IPsec offload code was updated accordingly for backward compatibility.
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/mlx5: Removed esp_id from struct mlx5_flow_act2022-09-07T13:02:08+00:00Lior Nahmansonliorna@nvidia.com2022-09-06T05:21:16+00:00urn:sha1:d1b2234b7fbf94348901bed4ea8d015c8a819d02
esp_id is no longer in used
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/mlx5: fs, allow flow table creation with a UID2022-07-17T18:54:14+00:00Mark Blochmbloch@nvidia.com2022-07-03T20:54:05+00:00urn:sha1:b0bb369ee451323968b31392a86398f15a2ba183
Add UID field to flow table attributes to allow creating flow tables
with a non default (zero) uid.
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
net/mlx5: fs, expose flow table ID to users2022-07-17T18:54:14+00:00Mark Blochmbloch@nvidia.com2022-07-03T20:54:04+00:00urn:sha1:6c27c56cdc69608211617eea217e1a6cecccc675
Expose the flow table ID to users. This will be used by downstream
patches to allow creating steering rules that point to a flow table ID.
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
net/mlx5: Add support EXECUTE_ASO action for flow entry2022-06-13T21:59:06+00:00Jianbo Liujianbol@nvidia.com2022-06-08T20:04:49+00:00urn:sha1:91707779a481aab9c7f1d7a5ea3033ce87dc4fd6
Attach flow meter to FTE with object id and index.
Use metadata register C5 to store the packet color meter result.
Signed-off-by: Jianbo Liu <jianbol@nvidia.com>
Reviewed-by: Roi Dayan <roid@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
net/mlx5: fs, add unused destination type2022-05-03T04:21:14+00:00Mark Blochmbloch@nvidia.com2022-03-15T14:08:23+00:00urn:sha1:6510bc0d7cb4119ebe10f9ab43aca6fd0e5f3e73
When the caller doesn't pass a destination fs_core will create a unused
rule just so a context can be returned. This unused rule
is zeroed out and its type is 0 which can be mixed up with
MLX5_FLOW_DESTINATION_TYPE_VPORT.
Create a dedicated type to differentiate between the two
named MLX5_FLOW_DESTINATION_TYPE_NONE.
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
net/mlx5: fs, split software and IFC flow destination definitions2022-05-03T04:21:13+00:00Mark Blochmbloch@nvidia.com2022-03-22T09:16:39+00:00urn:sha1:d639af621600dc52dd9ed0dcf62b22595f2f5b52
Separate flow destinations between software and IFC.
Flow destination type passed by callers was used as the input in
firmware commands and over the years software only types were added
which resulted in mixing between the two.
Create an IFC enum that contains only the flow destinations defined
when talking to the firmware.
Now that there is a proper software only enum for flow destinations
the hardcoded values can be removed as the values are no longer used
in firmware commands.
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
net/mlx5: Add ability to insert to specific flow group2022-02-23T23:21:58+00:00Mark Blochmbloch@nvidia.com2021-11-29T14:24:28+00:00urn:sha1:c2c922dae77f36e24d246c6e310cee0c61afc6fb
If the flow table isn't an autogroup the upper driver has to create the
flow groups explicitly. This information can't later be used when
creating rules to insert into a specific flow group. Allow such use case.
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>