From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: dev@dpdk.org
Subject: Re: [PATCH v2 01/10] ethdev: introduce flow pre-configuration hints
Date: Wed, 19 Jan 2022 16:07:05 +0300 (MSK) [thread overview]
Message-ID: <3d9945a0-bca4-559-88a1-864d90a11b44@oktetlabs.ru> (raw)
Hi,
> +Rules management configuration
> +------------------------------
> +
> +Configure flow rules management.
It is either "management OF ruleS" or "rule management".
Perhaps fix similar occurrences across the series.
> + /**
> + * Number of counter actions pre-configured.
> + * If set to 0, PMD will allocate counters dynamically.
> + * @see RTE_FLOW_ACTION_TYPE_COUNT
> + */
> + uint32_t nb_counters;
> + /**
> + * Number of aging actions pre-configured.
> + * If set to 0, PMD will allocate aging dynamically.
> + * @see RTE_FLOW_ACTION_TYPE_AGE
> + */
> + uint32_t nb_aging;
> + /**
> + * Number of traffic metering actions pre-configured.
> + * If set to 0, PMD will allocate meters dynamically.
> + * @see RTE_FLOW_ACTION_TYPE_METER
> + */
> + uint32_t nb_meters;
If duplication of the same description is undesirable,
consider adding a common description for these fields:
/**
* Resource preallocation settings. Use zero to
* request that allocations be done on demand.
*/
Instead of "nb_aging", perhaps consider something like "nb_age_timers".
> + * Configure flow rules module.
> + * To pre-allocate resources as per the flow port attributes
> + * this configuration function must be called before any flow rule is created.
> + * Must be called only after Ethernet device is configured, but may be called
> + * before or after the device is started as long as there are no flow rules.
> + * No other rte_flow function should be called while this function is invoked.
> + * This function can be called again to change the configuration.
> + * Some PMDs may not support re-configuration at all,
> + * or may only allow increasing the number of resources allocated.
Consider:
* Pre-configure the port's flow API engine.
*
* This API can only be invoked before the application
* starts using the rest of the flow library functions.
*
* The API can be invoked multiple times to change the
* settings. The port, however, may reject the changes.
--
Ivan M.
next reply other threads:[~2022-01-19 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 13:07 Ivan Malov [this message]
2022-01-25 1:09 ` Alexander Kozyrev
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 4:48 [dpdk-dev] [RFC 0/3] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-01-18 15:30 ` [PATCH v2 00/10] " Alexander Kozyrev
2022-01-18 15:30 ` [PATCH v2 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-01-24 14:36 ` Jerin Jacob
2022-01-24 17:35 ` Thomas Monjalon
2022-01-24 17:46 ` Jerin Jacob
2022-01-24 18:08 ` Bruce Richardson
2022-01-25 1:14 ` Alexander Kozyrev
2022-01-25 15:58 ` Ori Kam
2022-01-25 18:09 ` Bruce Richardson
2022-01-25 18:14 ` Bruce Richardson
2022-01-26 9:45 ` Ori Kam
2022-01-26 10:52 ` Bruce Richardson
2022-01-26 11:21 ` Thomas Monjalon
2022-01-26 12:19 ` Ori Kam
2022-01-26 13:41 ` Bruce Richardson
2022-01-26 15:12 ` Ori Kam
2022-01-24 17:40 ` Ajit Khaparde
2022-01-25 1:28 ` Alexander Kozyrev
2022-01-25 18:44 ` Jerin Jacob
2022-01-26 22:02 ` Alexander Kozyrev
2022-01-27 9:34 ` Jerin Jacob
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=3d9945a0-bca4-559-88a1-864d90a11b44@oktetlabs.ru \
--to=ivan.malov@oktetlabs.ru \
--cc=dev@dpdk.org \
/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).