From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: <dev@dpdk.org>, <dsosnowski@nvidia.com>, <orika@nvidia.com>,
<thomas@monjalon.net>, <matan@nvidia.com>, <ferruh.yigit@amd.com>
Subject: Re: [RFC] ethdev: jump to table support
Date: Thu, 22 Aug 2024 16:09:53 -0700 [thread overview]
Message-ID: <20240822160953.3c7d3d52@hermes.local> (raw)
In-Reply-To: <20240822202753.3856703-1-akozyrev@nvidia.com>
On Thu, 22 Aug 2024 23:27:53 +0300
Alexander Kozyrev <akozyrev@nvidia.com> wrote:
> +/**
> + * @warning
> + * @b EXPERIMENTAL: this API may change without prior notice.
> + *
> + * Enqueue rule creation operation.
> + *
> + * @param port_id
> + * Port identifier of Ethernet device.
> + * @param queue_id
> + * Flow queue used to insert the rule.
> + * @param[in] op_attr
> + * Rule creation operation attributes.
> + * @param[in] template_table
> + * Template table to select templates from.
> + * @param[in] rule_index
> + * Rule index in the table.
> + * Inserting a rule to already occupied index results in undefined behavior.
> + * @param[in] pattern
> + * List of pattern items to be used.
> + * The list order should match the order in the pattern template.
> + * The spec is the only relevant member of the item that is being used.
> + * @param[in] pattern_template_index
> + * Pattern template index in the table.
> + * @param[in] actions
> + * List of actions to be used.
> + * The list order should match the order in the actions template.
> + * @param[in] actions_template_index
> + * Actions template index in the table.
> + * @param[in] user_data
> + * The user data that will be returned on the completion events.
> + * @param[out] error
> + * Perform verbose error reporting if not NULL.
> + * PMDs initialize this structure in case of error only.
> + *
> + * @return
> + * Handle on success, NULL otherwise and rte_errno is set.
> + * The rule handle doesn't mean that the rule has been populated.
> + * Only completion result indicates that if there was success or failure.
> + */
> +__rte_experimental
> +struct rte_flow *
> +rte_flow_async_create_by_index_with_pattern(uint16_t port_id,
> + uint32_t queue_id,
> + const struct rte_flow_op_attr *op_attr,
> + struct rte_flow_template_table *template_table,
> + uint32_t rule_index,
> + const struct rte_flow_item pattern[],
> + uint8_t pattern_template_index,
> + const struct rte_flow_action actions[],
> + uint8_t actions_template_index,
> + void *user_data,
> + struct rte_flow_error *error);
Choosing names is hard, long names are not always better. Can you think
of a more concise name?
Je n’ai fait celle-ci plus longue que parce que je n’ai pas eu le loisir de la faire plus courte. -- Blaise Pascal
next prev parent reply other threads:[~2024-08-22 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 20:27 Alexander Kozyrev
2024-08-22 23:09 ` Stephen Hemminger [this message]
2024-09-04 21:05 ` Alexander Kozyrev
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=20240822160953.3c7d3d52@hermes.local \
--to=stephen@networkplumber.org \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--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).