1 /* SPDX-License-Identifier: BSD-3-Clause
2 * Copyright(C) 2019 Marvell International Ltd.
3 * Copyright 2020 Mellanox Technologies, Ltd
4 * Copyright(c) 2020 Intel Corporation
7 #ifndef _RTE_REGEXDEV_H_
8 #define _RTE_REGEXDEV_H_
13 * RTE RegEx Device API
15 * Defines RTE RegEx Device APIs for RegEx operations and its provisioning.
17 * The RegEx Device API is composed of two parts:
19 * - The application-oriented RegEx API that includes functions to setup
20 * a RegEx device (configure it, setup its queue pairs and start it),
21 * update the rule database and so on.
23 * - The driver-oriented RegEx API that exports a function allowing
24 * a RegEx poll Mode Driver (PMD) to simultaneously register itself as
25 * a RegEx device driver.
27 * RegEx device components and definitions:
31 * | o---------+ rte_regexdev_[en|de]queue_burst()
32 * | PCRE based o------+ | |
33 * | RegEx pattern | | | +--------+ |
34 * | matching engine o------+--+--o | | +------+
35 * | | | | | queue |<==o===>|Core 0|
36 * | o----+ | | | pair 0 | | |
37 * | | | | | +--------+ +------+
38 * +-----------------+ | | |
40 * | | | | | | +------+
41 * | | +--+--o queue |<======>|Core 1|
42 * Rule|Database | | | pair 1 | | |
43 * +------+----------+ | | +--------+ +------+
45 * | +-------------+ | | | +--------+ +------+
46 * | | Rules 0..n | | | | | | |Core 2|
47 * | +-------------+ | | +--o queue |<======>| |
48 * | Group 1 | | | pair 2 | +------+
49 * | +-------------+ | | +--------+
50 * | | Rules 0..n | | |
51 * | +-------------+ | | +--------+
52 * | Group 2 | | | | +------+
53 * | +-------------+ | | | queue |<======>|Core n|
54 * | | Rules 0..n | | +-------o pair n | | |
55 * | +-------------+ | +--------+ +------+
57 * | +-------------+ |<-------rte_regexdev_rule_db_update()
58 * | | | |<-------rte_regexdev_rule_db_compile_activate()
59 * | | Rules 0..n | |<-------rte_regexdev_rule_db_import()
60 * | +-------------+ |------->rte_regexdev_rule_db_export()
63 * RegEx: A regular expression is a concise and flexible means for matching
64 * strings of text, such as particular characters, words, or patterns of
65 * characters. A common abbreviation for this is “RegEx”.
67 * RegEx device: A hardware or software-based implementation of RegEx
68 * device API for PCRE based pattern matching syntax and semantics.
70 * PCRE RegEx syntax and semantics specification:
71 * http://regexkit.sourceforge.net/Documentation/pcre/pcrepattern.html
73 * RegEx queue pair: Each RegEx device should have one or more queue pair to
74 * transmit a burst of pattern matching request and receive a burst of
75 * receive the pattern matching response. The pattern matching request/response
76 * embedded in *rte_regex_ops* structure.
78 * Rule: A pattern matching rule expressed in PCRE RegEx syntax along with
79 * Match ID and Group ID to identify the rule upon the match.
81 * Rule database: The RegEx device accepts regular expressions and converts them
82 * into a compiled rule database that can then be used to scan data.
83 * Compilation allows the device to analyze the given pattern(s) and
84 * pre-determine how to scan for these patterns in an optimized fashion that
85 * would be far too expensive to compute at run-time. A rule database contains
86 * a set of rules that compiled in device specific binary form.
88 * Match ID or Rule ID: A unique identifier provided at the time of rule
89 * creation for the application to identify the rule upon match.
91 * Group ID: Group of rules can be grouped under one group ID to enable
92 * rule isolation and effective pattern matching. A unique group identifier
93 * provided at the time of rule creation for the application to identify the
96 * Scan: A pattern matching request through *enqueue* API.
98 * It may possible that a given RegEx device may not support all the features
99 * of PCRE. The application may probe unsupported features through
100 * struct rte_regexdev_info::pcre_unsup_flags
102 * By default, all the functions of the RegEx Device API exported by a PMD
103 * are lock-free functions which assume to not be invoked in parallel on
104 * different logical cores to work on the same target object. For instance,
105 * the dequeue function of a PMD cannot be invoked in parallel on two logical
106 * cores to operates on same RegEx queue pair. Of course, this function
107 * can be invoked in parallel by different logical core on different queue pair.
108 * It is the responsibility of the upper level application to enforce this rule.
110 * In all functions of the RegEx API, the RegEx device is
111 * designated by an integer >= 0 named the device identifier *dev_id*
113 * At the RegEx driver level, RegEx devices are represented by a generic
114 * data structure of type *rte_regexdev*.
116 * RegEx devices are dynamically registered during the PCI/SoC device probing
117 * phase performed at EAL initialization time.
118 * When a RegEx device is being probed, a *rte_regexdev* structure and
119 * a new device identifier are allocated for that device. Then, the
120 * regexdev_init() function supplied by the RegEx driver matching the probed
121 * device is invoked to properly initialize the device.
123 * The role of the device init function consists of resetting the hardware or
124 * software RegEx driver implementations.
126 * If the device init operation is successful, the correspondence between
127 * the device identifier assigned to the new device and its associated
128 * *rte_regexdev* structure is effectively registered.
129 * Otherwise, both the *rte_regexdev* structure and the device identifier are
132 * The functions exported by the application RegEx API to setup a device
133 * designated by its device identifier must be invoked in the following order:
134 * - rte_regexdev_configure()
135 * - rte_regexdev_queue_pair_setup()
136 * - rte_regexdev_start()
138 * Then, the application can invoke, in any order, the functions
139 * exported by the RegEx API to enqueue pattern matching job, dequeue pattern
140 * matching response, get the stats, update the rule database,
141 * get/set device attributes and so on
143 * If the application wants to change the configuration (i.e. call
144 * rte_regexdev_configure() or rte_regexdev_queue_pair_setup()), it must call
145 * rte_regexdev_stop() first to stop the device and then do the reconfiguration
146 * before calling rte_regexdev_start() again. The enqueue and dequeue
147 * functions should not be invoked when the device is stopped.
149 * Finally, an application can close a RegEx device by invoking the
150 * rte_regexdev_close() function.
152 * Each function of the application RegEx API invokes a specific function
153 * of the PMD that controls the target device designated by its device
156 * For this purpose, all device-specific functions of a RegEx driver are
157 * supplied through a set of pointers contained in a generic structure of type
159 * The address of the *regexdev_ops* structure is stored in the *rte_regexdev*
160 * structure by the device init function of the RegEx driver, which is
161 * invoked during the PCI/SoC device probing phase, as explained earlier.
163 * In other words, each function of the RegEx API simply retrieves the
164 * *rte_regexdev* structure associated with the device identifier and
165 * performs an indirect invocation of the corresponding driver function
166 * supplied in the *regexdev_ops* structure of the *rte_regexdev* structure.
168 * For performance reasons, the address of the fast-path functions of the
169 * RegEx driver is not contained in the *regexdev_ops* structure.
170 * Instead, they are directly stored at the beginning of the *rte_regexdev*
171 * structure to avoid an extra indirect memory access during their invocation.
173 * RTE RegEx device drivers do not use interrupts for enqueue or dequeue
174 * operation. Instead, RegEx drivers export Poll-Mode enqueue and dequeue
175 * functions to applications.
177 * The *enqueue* operation submits a burst of RegEx pattern matching request
178 * to the RegEx device and the *dequeue* operation gets a burst of pattern
179 * matching response for the ones submitted through *enqueue* operation.
181 * Typical application utilisation of the RegEx device API will follow the
182 * following programming flow.
184 * - rte_regexdev_configure()
185 * - rte_regexdev_queue_pair_setup()
186 * - rte_regexdev_rule_db_update() Needs to invoke if precompiled rule database
187 * not provided in rte_regexdev_config::rule_db for rte_regexdev_configure()
188 * and/or application needs to update rule database.
189 * - rte_regexdev_rule_db_compile_activate() Needs to invoke if
190 * rte_regexdev_rule_db_update function was used.
191 * - Create or reuse exiting mempool for *rte_regex_ops* objects.
192 * - rte_regexdev_start()
193 * - rte_regexdev_enqueue_burst()
194 * - rte_regexdev_dequeue_burst()
201 #include <rte_common.h>
202 #include <rte_config.h>
204 #include <rte_errno.h>
205 #include <rte_mbuf.h>
206 #include <rte_memory.h>
208 #define RTE_REGEXDEV_NAME_MAX_LEN RTE_DEV_NAME_MAX_LEN
210 extern int rte_regexdev_logtype;
212 #define RTE_REGEXDEV_LOG(level, ...) \
213 rte_log(RTE_LOG_ ## level, rte_regexdev_logtype, "" __VA_ARGS__)
217 * @b EXPERIMENTAL: this API may change without prior notice.
219 * Get the total number of RegEx devices that have been successfully
223 * The total number of usable RegEx devices.
227 rte_regexdev_count(void);
231 * @b EXPERIMENTAL: this API may change without prior notice.
233 * Get the device identifier for the named RegEx device.
236 * RegEx device name to select the RegEx device identifier.
239 * Returns RegEx device identifier on success.
240 * - <0: Failure to find named RegEx device.
244 rte_regexdev_get_dev_id(const char *name);
246 /* Enumerates RegEx device capabilities */
247 #define RTE_REGEXDEV_CAPA_RUNTIME_COMPILATION_F (1ULL << 0)
248 /**< RegEx device does support compiling the rules at runtime unlike
249 * loading only the pre-built rule database using
250 * struct rte_regexdev_config::rule_db in rte_regexdev_configure()
252 * @see struct rte_regexdev_config::rule_db, rte_regexdev_configure()
253 * @see struct rte_regexdev_info::regexdev_capa
256 #define RTE_REGEXDEV_CAPA_SUPP_PCRE_START_ANCHOR_F (1ULL << 1)
257 /**< RegEx device support PCRE Anchor to start of match flag.
258 * Example RegEx is `/\Gfoo\d/`. Here `\G` asserts position at the end of the
259 * previous match or the start of the string for the first match.
260 * This position will change each time the RegEx is applied to the subject
261 * string. If the RegEx is applied to `foo1foo2Zfoo3` the first two matches will
262 * be successful for `foo1foo2` and fail for `Zfoo3`.
264 * @see struct rte_regexdev_info::regexdev_capa
267 #define RTE_REGEXDEV_CAPA_SUPP_PCRE_ATOMIC_GROUPING_F (1ULL << 2)
268 /**< RegEx device support PCRE Atomic grouping.
269 * Atomic groups are represented by `(?>)`. An atomic group is a group that,
270 * when the RegEx engine exits from it, automatically throws away all
271 * backtracking positions remembered by any tokens inside the group.
272 * Example RegEx is `a(?>bc|b)c` if the given patterns are `abc` and `abcc` then
273 * `a(bc|b)c` matches both where as `a(?>bc|b)c` matches only abcc because
274 * atomic groups don't allow backtracing back to `b`.
276 * @see struct rte_regexdev_info::regexdev_capa
279 #define RTE_REGEXDEV_SUPP_PCRE_BACKTRACKING_CTRL_F (1ULL << 3)
280 /**< RegEx device support PCRE backtracking control verbs.
281 * Some examples of backtracing verbs are (*COMMIT), (*ACCEPT), (*FAIL),
284 * @see struct rte_regexdev_info::regexdev_capa
287 #define RTE_REGEXDEV_SUPP_PCRE_CALLOUTS_F (1ULL << 4)
288 /**< RegEx device support PCRE callouts.
289 * PCRE supports calling external function in between matches by using `(?C)`.
290 * Example RegEx `ABC(?C)D` if a given patter is `ABCD` then the RegEx engine
291 * will parse ABC perform a userdefined callout and return a successful match at
294 * @see struct rte_regexdev_info::regexdev_capa
297 #define RTE_REGEXDEV_SUPP_PCRE_BACKREFERENCE_F (1ULL << 5)
298 /**< RegEx device support PCRE backreference.
299 * Example RegEx is `(\2ABC|(GHI))+` `\2` matches the same text as most recently
300 * matched by the 2nd capturing group i.e. `GHI`.
302 * @see struct rte_regexdev_info::regexdev_capa
305 #define RTE_REGEXDEV_SUPP_PCRE_GREEDY_F (1ULL << 6)
306 /**< RegEx device support PCRE Greedy mode.
307 * For example if the RegEx is `AB\d*?` then `*?` represents zero or unlimited
308 * matches. In greedy mode the pattern `AB12345` will be matched completely
309 * where as the ungreedy mode `AB` will be returned as the match.
311 * @see struct rte_regexdev_info::regexdev_capa
314 #define RTE_REGEXDEV_SUPP_PCRE_MATCH_ALL_F (1ULL << 7)
315 /**< RegEx device support match all mode.
316 * For example if the RegEx is `AB\d*?` then `*?` represents zero or unlimited
317 * matches. In match all mode the pattern `AB12345` will return 6 matches.
318 * AB, AB1, AB12, AB123, AB1234, AB12345.
320 * @see struct rte_regexdev_info::regexdev_capa
323 #define RTE_REGEXDEV_SUPP_PCRE_LOOKAROUND_ASRT_F (1ULL << 8)
324 /**< RegEx device support PCRE Lookaround assertions
325 * (Zero-width assertions). Example RegEx is `[a-z]+\d+(?=!{3,})` if
326 * the given pattern is `dwad1234!` the RegEx engine doesn't report any matches
327 * because the assert `(?=!{3,})` fails. The pattern `dwad123!!!` would return a
330 * @see struct rte_regexdev_info::regexdev_capa
333 #define RTE_REGEXDEV_SUPP_PCRE_MATCH_POINT_RST_F (1ULL << 9)
334 /**< RegEx device doesn't support PCRE match point reset directive.
335 * Example RegEx is `[a-z]+\K\d+` if the pattern is `dwad123`
336 * then even though the entire pattern matches only `123`
337 * is reported as a match.
339 * @see struct rte_regexdev_info::regexdev_capa
342 #define RTE_REGEXDEV_SUPP_NEWLINE_CONVENTIONS_F (1ULL << 10)
343 /**< RegEx support PCRE newline convention.
344 * Newline conventions are represented as follows:
345 * (*CR) carriage return
347 * (*CRLF) carriage return, followed by linefeed
348 * (*ANYCRLF) any of the three above
349 * (*ANY) all Unicode newline sequences
351 * @see struct rte_regexdev_info::regexdev_capa
354 #define RTE_REGEXDEV_SUPP_PCRE_NEWLINE_SEQ_F (1ULL << 11)
355 /**< RegEx device support PCRE newline sequence.
356 * The escape sequence `\R` will match any newline sequence.
357 * It is equivalent to: `(?>\r\n|\n|\x0b|\f|\r|\x85)`.
359 * @see struct rte_regexdev_info::regexdev_capa
362 #define RTE_REGEXDEV_SUPP_PCRE_POSSESSIVE_QUALIFIERS_F (1ULL << 12)
363 /**< RegEx device support PCRE possessive qualifiers.
364 * Example RegEx possessive qualifiers `*+`, `++`, `?+`, `{m,n}+`.
365 * Possessive quantifier repeats the token as many times as possible and it does
366 * not give up matches as the engine backtracks. With a possessive quantifier,
367 * the deal is all or nothing.
369 * @see struct rte_regexdev_info::regexdev_capa
372 #define RTE_REGEXDEV_SUPP_PCRE_SUBROUTINE_REFERENCES_F (1ULL << 13)
373 /**< RegEx device support PCRE Subroutine references.
374 * PCRE Subroutine references allow for sub patterns to be assessed
375 * as part of the RegEx. Example RegEx is `(foo|fuzz)\g<1>+bar` matches the
376 * pattern `foofoofuzzfoofuzzbar`.
378 * @see struct rte_regexdev_info::regexdev_capa
381 #define RTE_REGEXDEV_SUPP_PCRE_UTF_8_F (1ULL << 14)
382 /**< RegEx device support UTF-8 character encoding.
384 * @see struct rte_regexdev_info::pcre_unsup_flags
387 #define RTE_REGEXDEV_SUPP_PCRE_UTF_16_F (1ULL << 15)
388 /**< RegEx device support UTF-16 character encoding.
390 * @see struct rte_regexdev_info::regexdev_capa
393 #define RTE_REGEXDEV_SUPP_PCRE_UTF_32_F (1ULL << 16)
394 /**< RegEx device support UTF-32 character encoding.
396 * @see struct rte_regexdev_info::regexdev_capa
399 #define RTE_REGEXDEV_SUPP_PCRE_WORD_BOUNDARY_F (1ULL << 17)
400 /**< RegEx device support word boundaries.
401 * The meta character `\b` represents word boundary anchor.
403 * @see struct rte_regexdev_info::regexdev_capa
406 #define RTE_REGEXDEV_SUPP_PCRE_FORWARD_REFERENCES_F (1ULL << 18)
407 /**< RegEx device support Forward references.
408 * Forward references allow you to use a back reference to a group that appears
409 * later in the RegEx. Example RegEx is `(\3ABC|(DEF|(GHI)))+` matches the
410 * following string `GHIGHIABCDEF`.
412 * @see struct rte_regexdev_info::regexdev_capa
415 #define RTE_REGEXDEV_SUPP_MATCH_AS_END_F (1ULL << 19)
416 /**< RegEx device support match as end.
417 * Match as end means that the match result holds the end offset of the
418 * detected match. No len value is set.
419 * If the device doesn't support this feature it means the match
420 * result holds the starting position of match and the length of the match.
422 * @see struct rte_regexdev_info::regexdev_capa
425 #define RTE_REGEXDEV_SUPP_CROSS_BUFFER_F (1ULL << 20)
426 /**< RegEx device support cross buffer match.
427 * Cross buffer matching means that the match can be detected even if the
428 * string was started in previous buffer.
429 * In case the device is configured as RTE_REGEXDEV_CFG_MATCH_AS_END
430 * the end offset will be relative for the first packet.
431 * For example RegEx is ABC the first buffer is xxxx second buffer yyyA and
432 * the last buffer BCzz.
433 * In case the match as end is configured the end offset will be 10.
435 * @see RTE_REGEXDEV_CFG_MATCH_AS_END_F
436 * @see RTE_REGEXDEV_CFG_CROSS_BUFFER_SCAN_F
437 * @see RTE_REGEX_OPS_RSP_PMI_SOJ_F
438 * @see RTE_REGEX_OPS_RSP_PMI_EOJ_F
441 #define RTE_REGEXDEV_SUPP_MATCH_ALL_F (1ULL << 21)
442 /**< RegEx device support match all.
443 * Match all means that the RegEx engine will return all possible matches.
444 * For example, assume the RegEx is `A+b`, given the input AAAb the
445 * returned matches will be: Ab, AAb and AAAb.
447 * @see RTE_REGEXDEV_CFG_MATCH_ALL_F
450 /* Enumerates PCRE rule flags */
451 #define RTE_REGEX_PCRE_RULE_ALLOW_EMPTY_F (1ULL << 0)
452 /**< When this flag is set, the pattern that can match against an empty string,
453 * such as `.*` are allowed.
455 * @see struct rte_regexdev_info::rule_flags
456 * @see struct rte_regexdev_rule::rule_flags
459 #define RTE_REGEX_PCRE_RULE_ANCHORED_F (1ULL << 1)
460 /**< When this flag is set, the pattern is forced to be "anchored", that is, it
461 * is constrained to match only at the first matching point in the string that
462 * is being searched. Similar to `^` and represented by `\A`.
464 * @see struct rte_regexdev_info::rule_flags
465 * @see struct rte_regexdev_rule::rule_flags
468 #define RTE_REGEX_PCRE_RULE_CASELESS_F (1ULL << 2)
469 /**< When this flag is set, letters in the pattern match both upper and lower
470 * case letters in the subject.
472 * @see struct rte_regexdev_info::rule_flags
473 * @see struct rte_regexdev_rule::rule_flags
476 #define RTE_REGEX_PCRE_RULE_DOTALL_F (1ULL << 3)
477 /**< When this flag is set, a dot metacharacter in the pattern matches any
478 * character, including one that indicates a newline.
480 * @see struct rte_regexdev_info::rule_flags
481 * @see struct rte_regexdev_rule::rule_flags
484 #define RTE_REGEX_PCRE_RULE_DUPNAMES_F (1ULL << 4)
485 /**< When this flag is set, names used to identify capture groups need not be
488 * @see struct rte_regexdev_info::rule_flags
489 * @see struct rte_regexdev_rule::rule_flags
492 #define RTE_REGEX_PCRE_RULE_EXTENDED_F (1ULL << 5)
493 /**< When this flag is set, most white space characters in the pattern are
494 * totally ignored except when escaped or inside a character class.
496 * @see struct rte_regexdev_info::rule_flags
497 * @see struct rte_regexdev_rule::rule_flags
500 #define RTE_REGEX_PCRE_RULE_MATCH_UNSET_BACKREF_F (1ULL << 6)
501 /**< When this flag is set, a backreference to an unset capture group matches an
504 * @see struct rte_regexdev_info::rule_flags
505 * @see struct rte_regexdev_rule::rule_flags
508 #define RTE_REGEX_PCRE_RULE_MULTILINE_F (1ULL << 7)
509 /**< When this flag is set, the `^` and `$` constructs match immediately
510 * following or immediately before internal newlines in the subject string,
511 * respectively, as well as at the very start and end.
513 * @see struct rte_regexdev_info::rule_flags
514 * @see struct rte_regexdev_rule::rule_flags
517 #define RTE_REGEX_PCRE_RULE_NO_AUTO_CAPTURE_F (1ULL << 8)
518 /**< When this Flag is set, it disables the use of numbered capturing
519 * parentheses in the pattern. References to capture groups (backreferences or
520 * recursion/subroutine calls) may only refer to named groups, though the
521 * reference can be by name or by number.
523 * @see struct rte_regexdev_info::rule_flags
524 * @see struct rte_regexdev_rule::rule_flags
527 #define RTE_REGEX_PCRE_RULE_UCP_F (1ULL << 9)
528 /**< By default, only ASCII characters are recognized, When this flag is set,
529 * Unicode properties are used instead to classify characters.
531 * @see struct rte_regexdev_info::rule_flags
532 * @see struct rte_regexdev_rule::rule_flags
535 #define RTE_REGEX_PCRE_RULE_UNGREEDY_F (1ULL << 10)
536 /**< When this flag is set, the "greediness" of the quantifiers is inverted
537 * so that they are not greedy by default, but become greedy if followed by
540 * @see struct rte_regexdev_info::rule_flags
541 * @see struct rte_regexdev_rule::rule_flags
544 #define RTE_REGEX_PCRE_RULE_UTF_F (1ULL << 11)
545 /**< When this flag is set, RegEx engine has to regard both the pattern and the
546 * subject strings that are subsequently processed as strings of UTF characters
547 * instead of single-code-unit strings.
549 * @see struct rte_regexdev_info::rule_flags
550 * @see struct rte_regexdev_rule::rule_flags
553 #define RTE_REGEX_PCRE_RULE_NEVER_BACKSLASH_C_F (1ULL << 12)
554 /**< This flag locks out the use of `\C` in the pattern that is being compiled.
555 * This escape matches one data unit, even in UTF mode which can cause
556 * unpredictable behavior in UTF-8 or UTF-16 modes, because it may leave the
557 * current matching point in the mi:set hlsearchddle of a multi-code-unit
560 * @see struct rte_regexdev_info::rule_flags
561 * @see struct rte_regexdev_rule::rule_flags
565 * RegEx device information
567 struct rte_regexdev_info {
568 const char *driver_name; /**< RegEx driver name. */
569 struct rte_device *dev; /**< Device information. */
570 uint16_t max_matches;
571 /**< Maximum matches per scan supported by this device. */
572 uint16_t max_queue_pairs;
573 /**< Maximum queue pairs supported by this device. */
574 uint16_t max_payload_size;
575 /**< Maximum payload size for a pattern match request or scan.
576 * @see RTE_REGEXDEV_CFG_CROSS_BUFFER_SCAN_F
578 uint32_t max_rules_per_group;
579 /**< Maximum rules supported per group by this device. */
581 /**< Maximum groups supported by this device. */
582 uint32_t regexdev_capa;
583 /**< RegEx device capabilities. @see RTE_REGEXDEV_CAPA_* */
585 /**< Supported compiler rule flags.
586 * @see RTE_REGEX_PCRE_RULE_*, struct rte_regexdev_rule::rule_flags
592 * @b EXPERIMENTAL: this API may change without prior notice.
594 * Retrieve the contextual information of a RegEx device.
597 * The identifier of the device.
599 * @param[out] dev_info
600 * A pointer to a structure of type *rte_regexdev_info* to be filled with the
601 * contextual information of the device.
604 * - 0: Success, driver updates the contextual information of the RegEx device
605 * - <0: Error code returned by the driver info get function.
609 rte_regexdev_info_get(uint8_t dev_id, struct rte_regexdev_info *dev_info);
611 /* Enumerates RegEx device configuration flags */
612 #define RTE_REGEXDEV_CFG_CROSS_BUFFER_SCAN_F (1ULL << 0)
613 /**< Cross buffer scan refers to the ability to be able to detect
614 * matches that occur across buffer boundaries, where the buffers are related
615 * to each other in some way. Enable this flag when to scan payload size
616 * greater than struct rte_regexdev_info::max_payload_size and/or
617 * matches can present across scan buffer boundaries.
619 * @see struct rte_regexdev_info::max_payload_size
620 * @see struct rte_regexdev_config::dev_cfg_flags, rte_regexdev_configure()
621 * @see RTE_REGEX_OPS_RSP_PMI_SOJ_F
622 * @see RTE_REGEX_OPS_RSP_PMI_EOJ_F
625 #define RTE_REGEXDEV_CFG_MATCH_AS_END_F (1ULL << 1)
626 /**< Match as end is the ability to return the result as ending offset.
627 * When this flag is set, the result for each match will hold the ending
628 * offset of the match in end_offset.
629 * If this flag is not set, then the match result will hold the starting offset
630 * in start_offset, and the length of the match in len.
632 * @see RTE_REGEXDEV_SUPP_MATCH_AS_END_F
635 #define RTE_REGEXDEV_CFG_MATCH_ALL_F (1ULL << 2)
636 /**< Match all is the ability to return all possible results.
638 * @see RTE_REGEXDEV_SUPP_MATCH_ALL_F
641 /** RegEx device configuration structure */
642 struct rte_regexdev_config {
643 uint16_t nb_max_matches;
644 /**< Maximum matches per scan configured on this device.
645 * This value cannot exceed the *max_matches*
646 * which previously provided in rte_regexdev_info_get().
647 * The value 0 is allowed, in which case, value 1 used.
648 * @see struct rte_regexdev_info::max_matches
650 uint16_t nb_queue_pairs;
651 /**< Number of RegEx queue pairs to configure on this device.
652 * This value cannot exceed the *max_queue_pairs* which previously
653 * provided in rte_regexdev_info_get().
654 * @see struct rte_regexdev_info::max_queue_pairs
656 uint32_t nb_rules_per_group;
657 /**< Number of rules per group to configure on this device.
658 * This value cannot exceed the *max_rules_per_group*
659 * which previously provided in rte_regexdev_info_get().
660 * The value 0 is allowed, in which case,
661 * struct rte_regexdev_info::max_rules_per_group used.
662 * @see struct rte_regexdev_info::max_rules_per_group
665 /**< Number of groups to configure on this device.
666 * This value cannot exceed the *max_groups*
667 * which previously provided in rte_regexdev_info_get().
668 * @see struct rte_regexdev_info::max_groups
671 /**< Import initial set of prebuilt rule database on this device.
672 * The value NULL is allowed, in which case, the device will not
673 * be configured prebuilt rule database. Application may use
674 * rte_regexdev_rule_db_update() or rte_regexdev_rule_db_import() API
675 * to update or import rule database after the
676 * rte_regexdev_configure().
677 * @see rte_regexdev_rule_db_update(), rte_regexdev_rule_db_import()
679 uint32_t rule_db_len;
680 /**< Length of *rule_db* buffer. */
681 uint32_t dev_cfg_flags;
682 /**< RegEx device configuration flags, See RTE_REGEXDEV_CFG_* */
687 * @b EXPERIMENTAL: this API may change without prior notice.
689 * Configure a RegEx device.
691 * This function must be invoked first before any other function in the
692 * API. This function can also be re-invoked when a device is in the
695 * The caller may use rte_regexdev_info_get() to get the capability of each
696 * resources available for this regex device.
699 * The identifier of the device to configure.
701 * The RegEx device configuration structure.
704 * - 0: Success, device configured. Otherwise negative errno is returned.
708 rte_regexdev_configure(uint8_t dev_id, const struct rte_regexdev_config *cfg);
710 /* Enumerates RegEx queue pair configuration flags */
711 #define RTE_REGEX_QUEUE_PAIR_CFG_OOS_F (1ULL << 0)
712 /**< Out of order scan, If not set, a scan must retire after previously issued
713 * in-order scans to this queue pair. If set, this scan can be retired as soon
714 * as device returns completion. Application should not set out of order scan
715 * flag if it needs to maintain the ingress order of scan request.
717 * @see struct rte_regexdev_qp_conf::qp_conf_flags
718 * @see rte_regexdev_queue_pair_setup()
721 struct rte_regex_ops;
722 typedef void (*regexdev_stop_flush_t)(uint8_t dev_id, uint16_t qp_id,
723 struct rte_regex_ops *op);
724 /**< Callback function called during rte_regexdev_stop(), invoked once per
728 /** RegEx queue pair configuration structure */
729 struct rte_regexdev_qp_conf {
730 uint32_t qp_conf_flags;
731 /**< Queue pair config flags, See RTE_REGEX_QUEUE_PAIR_CFG_* */
733 /**< The number of descriptors to allocate for this queue pair. */
734 regexdev_stop_flush_t cb;
735 /**< Callback function called during rte_regexdev_stop(), invoked
736 * once per flushed regex op. Value NULL is allowed, in which case
737 * callback will not be invoked. This function can be used to properly
738 * dispose of outstanding regex ops from response queue,
739 * for example ops containing memory pointers.
740 * @see rte_regexdev_stop()
746 * @b EXPERIMENTAL: this API may change without prior notice.
748 * Allocate and set up a RegEx queue pair for a RegEx device.
751 * The identifier of the device.
752 * @param queue_pair_id
753 * The index of the RegEx queue pair to setup. The value must be in the range
754 * [0, nb_queue_pairs - 1] previously supplied to rte_regexdev_configure().
756 * The pointer to the configuration data to be used for the RegEx queue pair.
757 * NULL value is allowed, in which case default configuration used.
760 * 0 on success. Otherwise negative errno is returned.
764 rte_regexdev_queue_pair_setup(uint8_t dev_id, uint16_t queue_pair_id,
765 const struct rte_regexdev_qp_conf *qp_conf);
769 * @b EXPERIMENTAL: this API may change without prior notice.
771 * Start a RegEx device.
773 * The device start step is the last one and consists of setting the RegEx
774 * queues to start accepting the pattern matching scan requests.
776 * On success, all basic functions exported by the API (RegEx enqueue,
777 * RegEx dequeue and so on) can be invoked.
780 * RegEx device identifier.
783 * 0 on success. Otherwise negative errno is returned.
787 rte_regexdev_start(uint8_t dev_id);
791 * @b EXPERIMENTAL: this API may change without prior notice.
793 * Stop a RegEx device.
795 * Stop a RegEx device. The device can be restarted with a call to
796 * rte_regexdev_start().
798 * This function causes all queued response regex ops to be drained in the
799 * response queue. While draining ops out of the device,
800 * struct rte_regexdev_qp_conf::cb will be invoked for each ops.
803 * RegEx device identifier.
806 * 0 on success. Otherwise negative errno is returned.
810 rte_regexdev_stop(uint8_t dev_id);
814 * @b EXPERIMENTAL: this API may change without prior notice.
816 * Close a RegEx device. The device cannot be restarted!
819 * RegEx device identifier
822 * 0 on success. Otherwise negative errno is returned.
826 rte_regexdev_close(uint8_t dev_id);
828 /* Device get/set attributes */
830 /** Enumerates RegEx device attribute identifier */
831 enum rte_regexdev_attr_id {
832 RTE_REGEXDEV_ATTR_SOCKET_ID,
833 /**< The NUMA socket id to which the device is connected or
834 * a default of zero if the socket could not be determined.
838 RTE_REGEXDEV_ATTR_MAX_MATCHES,
839 /**< Maximum number of matches per scan.
840 * datatype: *uint8_t*
841 * operation: *get* and *set*
842 * @see RTE_REGEX_OPS_RSP_MAX_MATCH_F
844 RTE_REGEXDEV_ATTR_MAX_SCAN_TIMEOUT,
845 /**< Upper bound scan time in ns.
846 * datatype: *uint16_t*
847 * operation: *get* and *set*
848 * @see RTE_REGEX_OPS_RSP_MAX_SCAN_TIMEOUT_F
850 RTE_REGEXDEV_ATTR_MAX_PREFIX,
851 /**< Maximum number of prefix detected per scan.
852 * This would be useful for denial of service detection.
853 * datatype: *uint16_t*
854 * operation: *get* and *set*
855 * @see RTE_REGEX_OPS_RSP_MAX_PREFIX_F
861 * @b EXPERIMENTAL: this API may change without prior notice.
863 * Get an attribute from a RegEx device.
866 * RegEx device identifier.
868 * The attribute ID to retrieve.
870 * A pointer that will be filled in with the attribute
871 * value if successful.
874 * - 0: Successfully retrieved attribute value.
875 * - -EINVAL: Invalid device or *attr_id* provided, or *attr_value* is NULL.
876 * - -ENOTSUP: if the device doesn't support specific *attr_id*.
880 rte_regexdev_attr_get(uint8_t dev_id, enum rte_regexdev_attr_id attr_id,
885 * @b EXPERIMENTAL: this API may change without prior notice.
887 * Set an attribute to a RegEx device.
890 * RegEx device identifier.
892 * The attribute ID to retrieve.
894 * Pointer that will be filled in with the attribute value
895 * by the application.
898 * - 0: Successfully applied the attribute value.
899 * - -EINVAL: Invalid device or *attr_id* provided, or *attr_value* is NULL.
900 * - -ENOTSUP: if the device doesn't support specific *attr_id*.
904 rte_regexdev_attr_set(uint8_t dev_id, enum rte_regexdev_attr_id attr_id,
905 const void *attr_value);
907 /* Rule related APIs */
908 /** Enumerates RegEx rule operation. */
909 enum rte_regexdev_rule_op {
910 RTE_REGEX_RULE_OP_ADD,
911 /**< Add RegEx rule to rule database. */
912 RTE_REGEX_RULE_OP_REMOVE
913 /**< Remove RegEx rule from rule database. */
916 /** Structure to hold a RegEx rule attributes. */
917 struct rte_regexdev_rule {
918 enum rte_regexdev_rule_op op;
919 /**< OP type of the rule either a OP_ADD or OP_DELETE. */
921 /**< Group identifier to which the rule belongs to. */
923 /**< Rule identifier which is returned on successful match. */
924 const char *pcre_rule;
925 /**< Buffer to hold the PCRE rule. */
926 uint16_t pcre_rule_len;
927 /**< Length of the PCRE rule. */
929 /* PCRE rule flags. Supported device specific PCRE rules enumerated
930 * in struct rte_regexdev_info::rule_flags. For successful rule
931 * database update, application needs to provide only supported
933 * @See RTE_REGEX_PCRE_RULE_*, struct rte_regexdev_info::rule_flags
939 * @b EXPERIMENTAL: this API may change without prior notice.
941 * Update the local rule set.
942 * This functions only modify the rule set in memory.
943 * In order for the changes to take effect, the function
944 * rte_regexdev_rule_db_compile_active must be called.
947 * RegEx device identifier.
949 * Points to an array of *nb_rules* objects of type *rte_regexdev_rule*
950 * structure which contain the regex rules attributes to be updated
953 * The number of PCRE rules to update the rule database.
956 * The number of regex rules actually updated on the regex device's rule
957 * database. The return value can be less than the value of the *nb_rules*
958 * parameter when the regex devices fails to update the rule database or
959 * if invalid parameters are specified in a *rte_regexdev_rule*.
960 * If the return value is less than *nb_rules*, the remaining PCRE rules
961 * at the end of *rules* are not consumed and the caller has to take
962 * care of them and rte_errno is set accordingly.
963 * Possible errno values include:
964 * - -EINVAL: Invalid device ID or rules is NULL
965 * - -ENOTSUP: The last processed rule is not supported on this device.
966 * - -ENOSPC: No space available in rule database.
968 * @see rte_regexdev_rule_db_import(), rte_regexdev_rule_db_export(),
969 * rte_regexdev_rule_db_compile_activate()
973 rte_regexdev_rule_db_update(uint8_t dev_id,
974 const struct rte_regexdev_rule *rules,
979 * @b EXPERIMENTAL: this API may change without prior notice.
981 * Compile local rule set and burn the complied result to the
985 * RegEx device identifier.
988 * 0 on success, otherwise negative errno.
990 * @see rte_regexdev_rule_db_import(), rte_regexdev_rule_db_export(),
991 * rte_regexdev_rule_db_update()
995 rte_regexdev_rule_db_compile_activate(uint8_t dev_id);
999 * @b EXPERIMENTAL: this API may change without prior notice.
1001 * Import a prebuilt rule database from a buffer to a RegEx device.
1004 * RegEx device identifier.
1006 * Points to prebuilt rule database.
1007 * @param rule_db_len
1008 * Length of the rule database.
1011 * - 0: Successfully updated the prebuilt rule database.
1012 * - -EINVAL: Invalid device ID or rule_db is NULL
1013 * - -ENOTSUP: Rule database import is not supported on this device.
1014 * - -ENOSPC: No space available in rule database.
1016 * @see rte_regexdev_rule_db_update(), rte_regexdev_rule_db_export()
1020 rte_regexdev_rule_db_import(uint8_t dev_id, const char *rule_db,
1021 uint32_t rule_db_len);
1025 * @b EXPERIMENTAL: this API may change without prior notice.
1027 * Export the prebuilt rule database from a RegEx device to the buffer.
1030 * RegEx device identifier.
1031 * @param[out] rule_db
1032 * Block of memory to insert the rule database. Must be at least size in
1033 * capacity. If set to NULL, function returns required capacity.
1036 * - 0: Successfully exported the prebuilt rule database.
1037 * - size: If rule_db set to NULL then required capacity for *rule_db*
1038 * - -EINVAL: Invalid device ID
1039 * - -ENOTSUP: Rule database export is not supported on this device.
1041 * @see rte_regexdev_rule_db_update(), rte_regexdev_rule_db_import()
1045 rte_regexdev_rule_db_export(uint8_t dev_id, char *rule_db);
1047 /* Extended statistics */
1048 /** Maximum name length for extended statistics counters */
1049 #define RTE_REGEXDEV_XSTATS_NAME_SIZE 64
1052 * A name-key lookup element for extended statistics.
1054 * This structure is used to map between names and ID numbers
1055 * for extended RegEx device statistics.
1057 struct rte_regexdev_xstats_map {
1059 /**< xstat identifier */
1060 char name[RTE_REGEXDEV_XSTATS_NAME_SIZE];
1066 * @b EXPERIMENTAL: this API may change without prior notice.
1068 * Retrieve names of extended statistics of a regex device.
1071 * The identifier of the regex device.
1072 * @param[out] xstats_map
1073 * Block of memory to insert id and names into. Must be at least size in
1074 * capacity. If set to NULL, function returns required capacity.
1076 * - Positive value on success:
1077 * -The return value is the number of entries filled in the stats map.
1078 * -If xstats_map set to NULL then required capacity for xstats_map.
1079 * - Negative value on error:
1080 * -ENODEV for invalid *dev_id*
1081 * -ENOTSUP if the device doesn't support this function.
1085 rte_regexdev_xstats_names_get(uint8_t dev_id,
1086 struct rte_regexdev_xstats_map *xstats_map);
1090 * @b EXPERIMENTAL: this API may change without prior notice.
1092 * Retrieve extended statistics of an regex device.
1095 * The identifier of the device.
1097 * The id numbers of the stats to get. The ids can be got from the stat
1098 * position in the stat list from rte_regexdev_xstats_names_get(), or
1099 * by using rte_regexdev_xstats_by_name_get().
1101 * The values for each stats request by ID.
1103 * The number of stats requested.
1105 * - Positive value: number of stat entries filled into the values array
1106 * - Negative value on error:
1107 * -ENODEV for invalid *dev_id*
1108 * -ENOTSUP if the device doesn't support this function.
1112 rte_regexdev_xstats_get(uint8_t dev_id, const uint16_t *ids,
1113 uint64_t *values, uint16_t nb_values);
1117 * @b EXPERIMENTAL: this API may change without prior notice.
1119 * Retrieve the value of a single stat by requesting it by name.
1122 * The identifier of the device.
1124 * The stat name to retrieve.
1126 * If non-NULL, the numerical id of the stat will be returned, so that further
1127 * requests for the stat can be got using rte_regexdev_xstats_get, which will
1128 * be faster as it doesn't need to scan a list of names for the stat.
1130 * Must be non-NULL, retrieved xstat value will be stored in this address.
1133 * - 0: Successfully retrieved xstat value.
1134 * - -EINVAL: invalid parameters
1135 * - -ENOTSUP: if not supported.
1139 rte_regexdev_xstats_by_name_get(uint8_t dev_id, const char *name,
1140 uint16_t *id, uint64_t *value);
1144 * @b EXPERIMENTAL: this API may change without prior notice.
1146 * Reset the values of the xstats of the selected component in the device.
1149 * The identifier of the device.
1151 * Selects specific statistics to be reset. When NULL, all statistics will be
1152 * reset. If non-NULL, must point to array of at least *nb_ids* size.
1154 * The number of ids available from the *ids* array. Ignored when ids is NULL.
1157 * - 0: Successfully reset the statistics to zero.
1158 * - -EINVAL: invalid parameters.
1159 * - -ENOTSUP: if not supported.
1163 rte_regexdev_xstats_reset(uint8_t dev_id, const uint16_t *ids,
1168 * @b EXPERIMENTAL: this API may change without prior notice.
1170 * Trigger the RegEx device self test.
1173 * The identifier of the device.
1175 * - 0: Selftest successful.
1176 * - -ENOTSUP if the device doesn't support selftest.
1177 * - other values < 0 on failure.
1181 rte_regexdev_selftest(uint8_t dev_id);
1185 * @b EXPERIMENTAL: this API may change without prior notice.
1187 * Dump internal information about *dev_id* to the FILE* provided in *f*.
1190 * The identifier of the device.
1192 * A pointer to a file for output.
1195 * 0 on success, negative errno on failure.
1199 rte_regexdev_dump(uint8_t dev_id, FILE *f);
1201 /* Fast path APIs */
1204 * The generic *rte_regexdev_match* structure to hold the RegEx match
1206 * @see struct rte_regex_ops::matches
1208 struct rte_regexdev_match {
1213 uint32_t rule_id:20;
1214 /**< Rule identifier to which the pattern matched.
1215 * @see struct rte_regexdev_rule::rule_id
1217 uint32_t group_id:12;
1218 /**< Group identifier of the rule which the pattern
1219 * matched. @see struct rte_regexdev_rule::group_id
1221 uint16_t start_offset;
1222 /**< Starting Byte Position for matched rule. */
1226 /**< Length of match in bytes */
1227 uint16_t end_offset;
1228 /**< The end offset of the match. In case
1229 * MATCH_AS_END configuration is enabled.
1230 * @see RTE_REGEXDEV_CFG_MATCH_AS_END
1237 /* Enumerates RegEx request flags. */
1238 #define RTE_REGEX_OPS_REQ_GROUP_ID0_VALID_F (1 << 0)
1239 /**< Set when struct rte_regexdev_rule::group_id0 is valid. */
1241 #define RTE_REGEX_OPS_REQ_GROUP_ID1_VALID_F (1 << 1)
1242 /**< Set when struct rte_regexdev_rule::group_id1 is valid. */
1244 #define RTE_REGEX_OPS_REQ_GROUP_ID2_VALID_F (1 << 2)
1245 /**< Set when struct rte_regexdev_rule::group_id2 is valid. */
1247 #define RTE_REGEX_OPS_REQ_GROUP_ID3_VALID_F (1 << 3)
1248 /**< Set when struct rte_regexdev_rule::group_id3 is valid. */
1250 #define RTE_REGEX_OPS_REQ_STOP_ON_MATCH_F (1 << 4)
1251 /**< The RegEx engine will stop scanning and return the first match. */
1253 #define RTE_REGEX_OPS_REQ_MATCH_HIGH_PRIORITY_F (1 << 5)
1254 /**< In High Priority mode a maximum of one match will be returned per scan to
1255 * reduce the post-processing required by the application. The match with the
1256 * lowest Rule id, lowest start pointer and lowest match length will be
1259 * @see struct rte_regex_ops::nb_actual_matches
1260 * @see struct rte_regex_ops::nb_matches
1264 /* Enumerates RegEx response flags. */
1265 #define RTE_REGEX_OPS_RSP_PMI_SOJ_F (1 << 0)
1266 /**< Indicates that the RegEx device has encountered a partial match at the
1267 * start of scan in the given buffer.
1269 * @see RTE_REGEXDEV_CFG_CROSS_BUFFER_SCAN_F
1272 #define RTE_REGEX_OPS_RSP_PMI_EOJ_F (1 << 1)
1273 /**< Indicates that the RegEx device has encountered a partial match at the
1274 * end of scan in the given buffer.
1276 * @see RTE_REGEXDEV_CFG_CROSS_BUFFER_SCAN_F
1279 #define RTE_REGEX_OPS_RSP_MAX_SCAN_TIMEOUT_F (1 << 2)
1280 /**< Indicates that the RegEx device has exceeded the max timeout while
1281 * scanning the given buffer.
1283 * @see RTE_REGEXDEV_ATTR_MAX_SCAN_TIMEOUT
1286 #define RTE_REGEX_OPS_RSP_MAX_MATCH_F (1 << 3)
1287 /**< Indicates that the RegEx device has exceeded the max matches while
1288 * scanning the given buffer.
1290 * @see RTE_REGEXDEV_ATTR_MAX_MATCHES
1293 #define RTE_REGEX_OPS_RSP_MAX_PREFIX_F (1 << 4)
1294 /**< Indicates that the RegEx device has reached the max allowed prefix length
1295 * while scanning the given buffer.
1297 * @see RTE_REGEXDEV_ATTR_MAX_PREFIX
1301 * The generic *rte_regex_ops* structure to hold the RegEx attributes
1302 * for enqueue and dequeue operation.
1304 struct rte_regex_ops {
1307 /**< Request flags for the RegEx ops.
1308 * @see RTE_REGEX_OPS_REQ_*
1311 /**< Response flags for the RegEx ops.
1312 * @see RTE_REGEX_OPS_RSP_*
1314 uint16_t nb_actual_matches;
1315 /**< The total number of actual matches detected by the Regex device.*/
1316 uint16_t nb_matches;
1317 /**< The total number of matches returned by the RegEx device for this
1318 * scan. The size of *rte_regex_ops::matches* zero length array will be
1321 * @see struct rte_regex_ops::matches, struct rte_regexdev_match
1325 struct rte_mbuf *mbuf; /**< source mbuf, to search in. */
1329 /**< First group_id to match the rule against. At minimum one group
1330 * should be valid. Behaviour is undefined non of the groups are valid.
1332 * @see RTE_REGEX_OPS_REQ_GROUP_ID0_VALID_F
1335 /**< Second group_id to match the rule against.
1337 * @see RTE_REGEX_OPS_REQ_GROUP_ID1_VALID_F
1340 /**< Third group_id to match the rule against.
1342 * @see RTE_REGEX_OPS_REQ_GROUP_ID2_VALID_F
1345 /**< Forth group_id to match the rule against.
1347 * @see RTE_REGEX_OPS_REQ_GROUP_ID3_VALID_F
1354 /**< Application specific opaque value. An application may use
1355 * this field to hold application specific value to share
1356 * between dequeue and enqueue operation.
1357 * Implementation should not modify this field.
1360 /**< Pointer representation of *user_id* */
1366 uint64_t cross_buf_id;
1367 /**< ID used by the RegEx device in order to support cross
1369 * This ID is returned from the RegEx device on the dequeue
1370 * function. The application must send it back when calling
1371 * enqueue with the following packet.
1373 void *cross_buf_ptr;
1374 /**< Pointer representation of *corss_buf_id* */
1378 struct rte_regexdev_match matches[];
1379 /**< Zero length array to hold the match tuples.
1380 * The struct rte_regex_ops::nb_matches value holds the number of
1381 * elements in this array.
1383 * @see struct rte_regex_ops::nb_matches
1387 #include "rte_regexdev_core.h"
1391 * @b EXPERIMENTAL: this API may change without prior notice.
1393 * Enqueue a burst of scan request on a RegEx device.
1395 * The rte_regexdev_enqueue_burst() function is invoked to place
1396 * regex operations on the queue *qp_id* of the device designated by
1399 * The *nb_ops* parameter is the number of operations to process which are
1400 * supplied in the *ops* array of *rte_regexdev_op* structures.
1402 * The rte_regexdev_enqueue_burst() function returns the number of
1403 * operations it actually enqueued for processing. A return value equal to
1404 * *nb_ops* means that all packets have been enqueued.
1407 * The identifier of the device.
1409 * The index of the queue pair which packets are to be enqueued for
1410 * processing. The value must be in the range [0, nb_queue_pairs - 1]
1411 * previously supplied to rte_regexdev_configure().
1413 * The address of an array of *nb_ops* pointers to *rte_regexdev_op*
1414 * structures which contain the regex operations to be processed.
1416 * The number of operations to process.
1419 * The number of operations actually enqueued on the regex device. The return
1420 * value can be less than the value of the *nb_ops* parameter when the
1421 * regex devices queue is full or if invalid parameters are specified in
1422 * a *rte_regexdev_op*. If the return value is less than *nb_ops*, the
1423 * remaining ops at the end of *ops* are not consumed and the caller has
1424 * to take care of them.
1428 rte_regexdev_enqueue_burst(uint8_t dev_id, uint16_t qp_id,
1429 struct rte_regex_ops **ops, uint16_t nb_ops);
1433 * @b EXPERIMENTAL: this API may change without prior notice.
1435 * Dequeue a burst of scan response from a queue on the RegEx device.
1436 * The dequeued operation are stored in *rte_regexdev_op* structures
1437 * whose pointers are supplied in the *ops* array.
1439 * The rte_regexdev_dequeue_burst() function returns the number of ops
1440 * actually dequeued, which is the number of *rte_regexdev_op* data structures
1441 * effectively supplied into the *ops* array.
1443 * A return value equal to *nb_ops* indicates that the queue contained
1444 * at least *nb_ops* operations, and this is likely to signify that other
1445 * processed operations remain in the devices output queue. Applications
1446 * implementing a "retrieve as many processed operations as possible" policy
1447 * can check this specific case and keep invoking the
1448 * rte_regexdev_dequeue_burst() function until a value less than
1449 * *nb_ops* is returned.
1451 * The rte_regexdev_dequeue_burst() function does not provide any error
1452 * notification to avoid the corresponding overhead.
1455 * The RegEx device identifier
1457 * The index of the queue pair from which to retrieve processed packets.
1458 * The value must be in the range [0, nb_queue_pairs - 1] previously
1459 * supplied to rte_regexdev_configure().
1461 * The address of an array of pointers to *rte_regexdev_op* structures
1462 * that must be large enough to store *nb_ops* pointers in it.
1464 * The maximum number of operations to dequeue.
1467 * The number of operations actually dequeued, which is the number
1468 * of pointers to *rte_regexdev_op* structures effectively supplied to the
1469 * *ops* array. If the return value is less than *nb_ops*, the remaining
1470 * ops at the end of *ops* are not consumed and the caller has to take care
1475 rte_regexdev_dequeue_burst(uint8_t dev_id, uint16_t qp_id,
1476 struct rte_regex_ops **ops, uint16_t nb_ops);
1482 #endif /* _RTE_REGEXDEV_H_ */