From: Rongwei Liu <rongweil@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH v1] net/mlx5: enable hint in async table
Date: Mon, 6 Mar 2023 08:22:09 +0000 [thread overview]
Message-ID: <BN9PR12MB527305171A7F2A73BD9E8F59ABB69@BN9PR12MB5273.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230216054923.3973237-1-rongweil@nvidia.com>
@Slava Ovsiienko Can you help review and ACK?
BR
Rongwei
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Thursday, February 16, 2023 13:49
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Cc: Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v1] net/mlx5: enable hint in async table
>
> External email: Use caution opening links or attachments
>
>
> Driver gets the hint value from rte_table_attr for async flow.
> Parse the value and pass the supported value to hardware accordingly.
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow_hw.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_hw.c
> b/drivers/net/mlx5/mlx5_flow_hw.c index b67b33bc22..06d6909974 100644
> --- a/drivers/net/mlx5/mlx5_flow_hw.c
> +++ b/drivers/net/mlx5/mlx5_flow_hw.c
> @@ -3102,6 +3102,15 @@ flow_hw_table_create(struct rte_eth_dev *dev,
> matcher_attr.optimize_using_rule_idx = true;
> matcher_attr.mode = MLX5DR_MATCHER_RESOURCE_MODE_RULE;
> matcher_attr.rule.num_log = rte_log2_u32(nb_flows);
> + /* Parse hints information. */
> + if (attr->specialize) {
> + if (attr->specialize ==
> RTE_FLOW_TABLE_SPECIALIZE_TRANSFER_WIRE_ORIG)
> + matcher_attr.optimize_flow_src =
> MLX5DR_MATCHER_FLOW_SRC_WIRE;
> + else if (attr->specialize ==
> RTE_FLOW_TABLE_SPECIALIZE_TRANSFER_VPORT_ORIG)
> + matcher_attr.optimize_flow_src =
> MLX5DR_MATCHER_FLOW_SRC_VPORT;
> + else
> + DRV_LOG(INFO, "Unsupported hint value %x", attr->specialize);
> + }
> /* Build the item template. */
> for (i = 0; i < nb_item_templates; i++) {
> uint32_t ret;
> --
> 2.27.0
next prev parent reply other threads:[~2023-03-06 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 5:49 Rongwei Liu
2023-03-06 8:22 ` Rongwei Liu [this message]
2023-03-06 11:36 ` [PATCH v2] " Rongwei Liu
2023-03-06 11:59 ` Slava Ovsiienko
2023-03-07 9:02 ` Raslan Darawsheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN9PR12MB527305171A7F2A73BD9E8F59ABB69@BN9PR12MB5273.namprd12.prod.outlook.com \
--to=rongweil@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).