Home
last modified time | relevance | path

Searched refs:structure (Results 1 – 25 of 103) sorted by relevance

12345

/dpdk/lib/cmdline/
H A Dcmdline_parse_ipaddr.h48 #define TOKEN_IPADDR_INITIALIZER(structure, field) \ argument
53 offsetof(structure, field), /* offset */ \
62 #define TOKEN_IPV4_INITIALIZER(structure, field) \ argument
67 offsetof(structure, field), /* offset */ \
75 #define TOKEN_IPV6_INITIALIZER(structure, field) \ argument
80 offsetof(structure, field), /* offset */ \
88 #define TOKEN_IPNET_INITIALIZER(structure, field) \ argument
93 offsetof(structure, field), /* offset */ \
103 #define TOKEN_IPV4NET_INITIALIZER(structure, field) \ argument
108 offsetof(structure, field), /* offset */ \
[all …]
H A Dcmdline_parse_etheraddr.h28 #define TOKEN_ETHERADDR_INITIALIZER(structure, field) \ argument
33 offsetof(structure, field), /* offset */ \
H A Dcmdline_parse_portlist.h37 #define TOKEN_PORTLIST_INITIALIZER(structure, field) \ argument
42 offsetof(structure, field), /* offset */ \
H A Dcmdline_parse_num.h44 #define TOKEN_NUM_INITIALIZER(structure, field, numtype) \ argument
49 offsetof(structure, field), /* offset */ \
H A Dcmdline_parse_string.h56 #define TOKEN_STRING_INITIALIZER(structure, field, string) \ argument
61 offsetof(structure, field), /* offset */ \
/dpdk/examples/cmdline/
H A Dparse_obj_list.h47 #define TOKEN_OBJ_LIST_INITIALIZER(structure, field, obj_list_ptr) \ argument
51 .offset = offsetof(structure, field), \
/dpdk/doc/guides/prog_guide/
H A Drib_lib.rst42 * Intermediate Nodes which are used internally to preserve the binary tree structure.
61 * ``rte_rib_lookup()``: Lookup an IP in the structure using longest match.
63 * ``rte_rib_lookup_exact()``: Lookup an IP in the structure using exact match.
65 * ``rte_rib_lookup_parent()``: Find a parent prefix within the structure.
67 * ``rte_rib_get_nxt()``: Traverse a subtree within the structure.
69 Given a RIB structure with the routes depicted in :numref:`figure_rib_internals`,
H A Drcu_lib.rst19 an element from a data structure, the writers cannot return the memory
25 the data structure but does not return the associated memory to the
68 for D1. i.e. for a given data structure Dx, any point in the thread execution
103 states. This will combine all the shared data structure accesses into a
108 In these use cases, a given data structure may not be used by all the
110 use the data structure to report their quiescent state. To provide the required
112 application can create one QS variable per data structure to help it track the
113 end of grace period for each data structure. This helps keep the length of grace
197 the application. When a writer deletes an entry from a data structure, the writer:
208 However, if this resource reclamation process were to be integrated in lock-free data structure lib…
[all …]
H A Dtimer_lib.rst30 …l pending timers for a core being maintained in order of timer expiry in a skiplist data structure.
37 A timer structure contains a special field called status,
57 the expiry time of the first list entry is maintained within the per-core timer list structure itse…
58 …-bit platforms, this value can be checked without the need to take a lock on the overall structure.
H A Dtelemetry_lib.rst51 which will decide what port information should fill the ``rte_tel_data`` structure.
82 utilities API to build up the data structure with the required information.
83 The telemetry library is then responsible for formatting the data structure
90 Some data will need to be formatted in a list structure. For example, if a
H A Dmember_lib.rst17 extension and generalization of a traditional filter structure (for example
20 structure that provides a "set-summary" on whether a member belongs to a set,
29 probabilistic membership data structure that is provided by the library. A
33 (and other) applications. It is a crucial structure to address performance and
95 probabilistic data structure that answers set membership queries (test whether
203 HTSS employs a similar but simpler data structure to a traditional hash table,
221 also supports a set-summary probabilistic data structure based on HTSS which
277 The ``rte_member_create()`` function is used to create a set-summary structure, the input parameter
340 set-summary structure for multiple matches. It
356 set-summary structure for multiple matches, each key lookup returns ALL the matches (possibly more
[all …]
H A Dring_lib.rst32 The advantages of this data structure over a linked list queue are as follows:
48 …shown in with consumer and producer head and tail pointers to objects stored in the data structure.
93 The ring structure is composed of two head and tail couples; one is used by producers and one is us…
98 and the content of ring structure is represented on the bottom of the figure.
128 The second step is to modify *ring->prod_head* in ring structure to point to the same location as p…
143 Once the object is added in the ring, ring->prod_tail in the ring structure is modified to point to…
181 The second step is to modify ring->cons_head in the ring structure to point to the same location as…
196 Finally, ring->cons_tail in the ring structure is modified to point to the same location as ring->c…
235 The second step is to modify ring->prod_head in the ring structure to point to the same location as…
H A Dflow_classify_lib.rst178 The ``rte_flow_classify_params`` structure must be initialised by the
232 The ``rte_flow_classify_table_params`` structure must be initialised by the
248 To create an ACL table the ``rte_table_acl_params`` structure must be
250 ``rte_flow_classify_table_params`` structure.
307 ``rte_eth_ntuple_filter`` structure.
327 structure populated by the ``classify_parse_ntuple_filter`` function which
H A Dmbuf_lib.rst15 The rte_mbuf header structure is kept as small as possible and currently uses
24 #. Embed metadata within a single memory buffer the structure followed by a fixed size area for th…
26 #. Use separate memory buffers for the metadata structure and for the packet data.
76 The rte_pktmbuf_init() function initializes some fields in the mbuf structure that
219 in the "dynamic space", by registering some room in the mbuf structure:
222 named area in the mbuf structure,
226 named bit in the mbuf structure,
H A Dipsec_lib.rst67 - prepare *rte_crypto_op* structure for each input packet
80 - prepare *rte_crypto_op* structure for each input packet
141 - prepare *rte_crypto_op* structure for each input packet
147 - prepare *rte_crypto_op* structure for each input packet
159 Value is an opaque user provided pointer to the user defined SA data structure.
H A Dbbdev.rst197 structure in the *DPDK API Reference*.
255 capabilities. The ``rte_bbdev_info`` structure provides two levels of
328 An encode bbdev operation is represented by ``rte_bbdev_enc_op`` structure,
408 The bbdev operation structure contains all the mutable data relating to
450 This structure has three elements:
528 The Turbo encode structure includes the ``input`` and ``output`` mbuf
603 Turbo encoding of Code Blocks in mbuf structure
630 The Turbo decode structure includes the ``input``, ``hard_output`` and
711 Turbo decoding of Code Blocks in mbuf structure
751 The structure passed for each LDPC encode operation is given below,
[all …]
/dpdk/doc/guides/rel_notes/
H A Drelease_17_08.rst101 * **Reorganized the symmetric crypto operation structure.**
111 * Removed AAD pointer and physical address from ``auth`` structure.
112 * Added ``aead`` structure, containing parameters for AEAD algorithms.
114 * **Reorganized the crypto operation structure.**
124 * **Reorganized the crypto symmetric session structure.**
256 ``rte_bus`` structure.
258 * Made ``rte_devargs`` structure internal device representation generic to
267 * **Reorganized the crypto symmetric session structure.**
270 structure, as described in the `New Features`_ section.
272 * **Reorganized the rte_crypto_sym_cipher_xform structure.**
[all …]
H A Drelease_21_11.rst449 * eal: Made ``rte_intr_handle`` structure definition hidden.
514 * cryptodev: A ``reserved`` byte from structure ``rte_crypto_op`` was
520 moved to the end of the structure and extended to ``uint32_t``.
525 * cryptodev: The structure ``rte_crypto_sym_vec`` was updated to add
531 TLB misses if any and aligns to memory structure of other subsystems.
576 * security: A new option ``iv_gen_disable`` was added in structure
580 * security: A new option ``tunnel_hdr_verify`` was added in structure
584 * security: A new option ``udp_ports_verify`` was added in structure
589 replace ``esn_soft_limit`` in IPsec configuration structure
598 * security: A new structure ``esn`` was added in structure
[all …]
H A Drelease_2_2.rst541 * The ethdev flow director structure ``rte_eth_fdir_flow_ext`` structure was
544 * The size of the ethdev structure ``rte_eth_hash_filter_info`` is changed
548 ``rte_eth_dev_info`` structure.
558 * The mbuf structure was changed to support the unified packet type.
563 * The LPM structure is changed. The deprecated field ``mem_location`` is
567 the LPM table parameter structure.
570 parameter structure for 8-byte key and 16-byte key extendable bucket
574 buffer has been adjusted to cover the packet mbuf structure.
582 the ``virtqueue`` field is moved to the end of virtio_net structure.
585 ``virtio_net_device_ops`` structure.
[all …]
H A Drelease_20_11.rst218 Now the user can create any structure of rte_flow
459 from the structure ``rte_mbuf``. It is replaced with dynamic fields.
461 * mbuf: Removed the field ``seqn`` from the structure ``rte_mbuf``.
464 * mbuf: Removed the field ``timestamp`` from the structure ``rte_mbuf``.
550 ``rte_fpga_lte_fec_configure`` and structure ``fpga_lte_fec_conf`` to
554 ``rte_fpga_5gnr_fec_configure`` and structure ``fpga_5gnr_fec_conf`` to
557 * rawdev: Added a structure size parameter to the functions
615 which was already an internal data structure.
625 * Added fields ``rx_seg`` and ``rx_nseg`` to ``rte_eth_rxconf`` structure
633 * Added new field ``has_vlan`` to structure ``rte_flow_item_eth``,
[all …]
/dpdk/doc/guides/sample_app_ug/
H A Dvmdq_forwarding.rst78 rte_eth_conf structure passed to the rte_eth_dev_configure() API.
80 a default structure is provided for VMDq configuration to be filled in later by the application.
84 :start-after: Default structure for VMDq. 8<
85 :end-before: >8 End of Empty vdmq configuration structure.
87 The get_eth_conf() function fills in an rte_eth_conf structure with the appropriate values,
H A Dvmdq_dcb_forwarding.rst94 rte_eth_conf structure passed to the rte_eth_dev_configure() API.
96 a default structure is provided for VMDQ and DCB configuration to be filled in later by the applica…
100 :start-after: Empty vmdq+dcb configuration structure. Filled in programmatically. 8<
101 :end-before: >8 End of empty vmdq+dcb configuration structure.
103 The get_eth_conf() function fills in an rte_eth_conf structure with the appropriate values,
113 so the pools parameter in the rte_eth_vmdq_dcb_conf structure is specified as a bitmask value.
H A Dlink_status_intr.rst106 The global configuration is stored in a static structure:
110 :start-after: Global configuration stored in a static structure. 8<
111 :end-before: >8 End of global configuration stored in a static structure.
118 The public interface rte_eth_link_get() just reads the link status in a global structure
167 The list of queues that must be polled for a given lcore is stored in a private structure called st…
177 The global configuration for the RX queues is stored in a static structure:
196 The global configuration for TX queues is stored in a static structure:
H A Dqos_metering.rst107 where this policy is implemented as a static structure, as follows:
111 :start-after: Policy implemented as a static structure. 8<
112 :end-before: >8 End of policy implemented as a static structure.
/dpdk/doc/guides/rawdevs/
H A Dioat.rst149 structure parameters used by some of the rawdev APIs for IOAT rawdev
173 be NULL, or else be set to point to a structure of type
175 input ring will be returned in that structure.
181 ``rte_rawdev_configure()`` API, which takes the same structure parameters
184 output, the ``dev_private`` structure element cannot be NULL, and must
185 point to a valid ``rte_ioat_rawdev_config`` structure, containing the ring
190 the configuration structure also.

12345