DPDK patches and discussions
 help / color / mirror / Atom feed
From: Xiaoyu Min <jackmin@nvidia.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [RFC 0/2] queue-based flow aged report
Date: Wed, 1 Jun 2022 15:39:17 +0800	[thread overview]
Message-ID: <cover.1654063912.git.jackmin@nvidia.com> (raw)
In-Reply-To: <cover.1649308627.git.jackmin@nvidia.com>

For the queue-based flow managemnt, application can operate the same flow
on the same queue.

For example, application create flow with age action, query aged flow,
and destroy aged flow. All operations of flow happens on the same queue.

In this case, the PMD could be more optimized since all operations of the
same flow happens in sequence.

The current flow aged report API hasn't queue parameter as same as other
queue-based flow management API.

This RFC propose to add new flow aged report API with queue parameter.
Keep the old one for compatibility.

v2:
  - Add new API for querying which queues have aged out flows instead of
    passing queue id via *ret_param* in event.
  - Use bit flags instead of enum
  - Fix typo and wording

Xiaoyu Min (2):
  ethdev: port flags for pre-configuration flow hints
  ethdev: queue-based flow aged report

 lib/ethdev/rte_flow.h        | 93 ++++++++++++++++++++++++++++++++++++
 lib/ethdev/rte_flow_driver.h | 13 +++++
 2 files changed, 106 insertions(+)

-- 
2.36.1


  parent reply	other threads:[~2022-06-01  7:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  5:30 Xiaoyu Min
2022-04-07  5:30 ` [RFC 1/2] ethdev: port flags for pre-configuration flow hints Xiaoyu Min
2022-04-07 11:27   ` Ori Kam
2022-04-07 13:01     ` Jack Min
2022-04-07 15:04   ` Stephen Hemminger
2022-04-08  2:35     ` Jack Min
2022-05-30 16:46   ` Thomas Monjalon
2022-05-31 10:47     ` Jack Min
2022-04-07  5:30 ` [RFC 2/2] ethdev: queue-based flow aged report Xiaoyu Min
2022-05-30 16:42   ` Thomas Monjalon
2022-05-31 11:06     ` Jack Min
2022-05-31 12:57       ` Thomas Monjalon
2022-06-01  7:39 ` Xiaoyu Min [this message]
2022-06-01  7:39   ` [RFC v2 1/2] ethdev: port flags for pre-configuration flow hints Xiaoyu Min
2022-06-01  9:03     ` Ori Kam
2022-06-01 18:20     ` Andrew Rybchenko
2022-06-02  5:50       ` Ori Kam
2022-06-02  9:38       ` Jack Min
2022-06-01  7:39   ` [RFC v2 2/2] ethdev: queue-based flow aged report Xiaoyu Min
2022-06-01 18:21     ` Andrew Rybchenko
2022-06-02  6:10       ` Ori Kam
2022-06-02 10:23         ` Jack Min
2022-06-06  9:47           ` Ori Kam
2022-06-02  9:39       ` Jack Min

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=cover.1654063912.git.jackmin@nvidia.com \
    --to=jackmin@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).