From: Alexander Kozyrev <akozyrev@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>
Subject: Re: [RFC] ethdev: jump to table support
Date: Wed, 4 Sep 2024 21:05:05 +0000 [thread overview]
Message-ID: <SA1PR12MB8641EB1FF055750BB063C3B4AF9C2@SA1PR12MB8641.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240822160953.3c7d3d52@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
>> +__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
I would love to get a shorter name, but that's the best one I came up with.
Do you have any alternative suggestions? I'm open to any ideas here.
[-- Attachment #2: Type: text/html, Size: 4355 bytes --]
prev parent reply other threads:[~2024-09-04 21:05 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
2024-09-04 21:05 ` Alexander Kozyrev [this message]
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=SA1PR12MB8641EB1FF055750BB063C3B4AF9C2@SA1PR12MB8641.namprd12.prod.outlook.com \
--to=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=stephen@networkplumber.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).