Searched hist:"482 db2f1" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/net/xfrm/ |
| H A D | xfrm_device.c | 482db2f1 Thu May 05 05:06:41 CDT 2022 Leon Romanovsky <leonro@nvidia.com> xfrm: store and rely on direction to construct offload flags
XFRM state doesn't need anything from flags except to understand
direction, so store it separately. For future patches, such change
will allow us to reuse xfrm_dev_offload for policy offload too, which
has three possible directions instead of two.
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
|
| H A D | xfrm_user.c | 482db2f1 Thu May 05 05:06:41 CDT 2022 Leon Romanovsky <leonro@nvidia.com> xfrm: store and rely on direction to construct offload flags
XFRM state doesn't need anything from flags except to understand
direction, so store it separately. For future patches, such change
will allow us to reuse xfrm_dev_offload for policy offload too, which
has three possible directions instead of two.
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
|
| /openbmc/linux/include/net/ |
| H A D | xfrm.h | 482db2f1 Thu May 05 05:06:41 CDT 2022 Leon Romanovsky <leonro@nvidia.com> xfrm: store and rely on direction to construct offload flags
XFRM state doesn't need anything from flags except to understand
direction, so store it separately. For future patches, such change
will allow us to reuse xfrm_dev_offload for policy offload too, which
has three possible directions instead of two.
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
|