From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Suanming Mou <suanmingm@nvidia.com>, Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@xilinx.com>,
Ray Kinsella <mdr@ashroe.eu>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] ethdev: add indirect action async query
Date: Wed, 28 Sep 2022 11:50:56 +0300 [thread overview]
Message-ID: <56b71bfd-8068-852d-922d-5fb9c05e90d9@oktetlabs.ru> (raw)
In-Reply-To: <20220920071141.21769-1-suanmingm@nvidia.com>
On 9/20/22 10:11, Suanming Mou wrote:
> As rte_flow_action_handle_create/destroy/update() have their own
> asynchronous rte_flow_async_action_handle_create/destroy/update()
> version functions to accelerate the indirect action operations in
> queue based flow engine. Currently, the asynchronous version query
> function for indirect action was missing.
>
> This patch adds the rte_flow_async_action_handle_query() function
> corresponds to rte_flow_action_handle_query(). The new asynchronous
> version function enables enqueue the query to the hardware similar
> as asynchronous flow management does and returns immediately to free
> the CPU for other tasks. Application can get the query results from
> rte_flow_pull() when the hardware completes its work.
>
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2022-09-28 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:28 [RFC] " Suanming Mou
2022-08-15 12:01 ` Ori Kam
2022-09-20 7:11 ` [PATCH v1] " Suanming Mou
2022-09-28 8:50 ` Andrew Rybchenko [this message]
2022-11-17 8:06 ` David Marchand
2022-11-17 8:18 ` Suanming Mou
2022-11-17 8:31 ` David Marchand
2022-11-17 8:40 ` Suanming Mou
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=56b71bfd-8068-852d-922d-5fb9c05e90d9@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=mdr@ashroe.eu \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@intel.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).