Home
last modified time | relevance | path

Searched refs:segment (Results 1 – 25 of 39) sorted by relevance

12

/dpdk/doc/guides/prog_guide/
H A Dgeneric_segmentation_offload_lib.rst92 The combination of the 'header' segment and the 'data' segment constitutes a
96 .. _figure_gso-output-segment-format:
98 .. figure:: img/gso-output-segment-format.*
101 Two-part GSO output segment
107 multi-segment mbuf.
115 amount of data contained within each output segment; i.e. each output segment
117 final output segment; if ``pkt_len`` % ``segsz``, then the final segment is
123 mbuf to the output segment; this additional segment then points to the next
130 output segment. In this example, the output segment needs to include data from
134 next input segment).
[all …]
H A Dmbuf_lib.rst84 For any newly-allocated mbuf, it contains one segment, with a length of 0.
117 An mbuf also contains the input port (where it comes from), and the number of segment mbufs in the …
177 - segment inner TCP::
H A Denv_abstraction_layer.rst205 much memory a DPDK application can have. DPDK memory is stored in segment lists,
206 each segment is strictly one physical page. It is possible to change the amount
210 * ``RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have
212 segment list can address
213 * ``RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment list
265 See :ref:`segment-file-descriptors` section
308 See :ref:`segment-file-descriptors` section
316 On Linux, in most cases, EAL will store segment file descriptors in EAL. This
350 allocated memory for DMA is also performed on any memory segment that is added
991 with ``FREE`` at the start of each virtually contiguous segment of memory.
H A Dbbdev.rst477 CBs. The first mbuf segment in the given chained mbuf represents the first piece
478 of the CB. Offset is only applicable to the first segment. ``length`` is the
485 contains one segment.
487 The output mbuf data though is always one segment, even if the input was a
495 In case of chained mbuf, this offset applies only to the first mbuf segment.
H A Devent_timer_adapter.rst302 /* Retransmit last packet (e.g. TCP segment). */
/dpdk/drivers/net/qede/base/
H A Decore_init_ops.c78 u16 i, segment; in ecore_init_rt() local
97 for (segment = 1; i + segment < size; segment++) in ecore_init_rt()
98 if (!p_valid[i + segment]) in ecore_init_rt()
103 addr + (i << 2), segment, in ecore_init_rt()
109 i += segment; in ecore_init_rt()
/dpdk/doc/guides/compressdevs/
H A Doverview.rst28 (i.e. single segment).
/dpdk/doc/guides/nics/
H A Dionic.rst31 The ionic PMD requires firmware which supports 16 segment transmit SGLs.
H A Dsfc_efx.rst436 (full-feature firmware variant only), TSO and multi-segment mbufs.
445 is even more faster then **ef10** but does not support multi-segment
447 **ef100** chooses EF100 native datapath which supports multi-segment
H A Dvmxnet3.rst74 multiple segment buffers are not supported.
/dpdk/doc/guides/rel_notes/
H A Drelease_21_08.rst160 * **Last mbuf segment not implicitly reset.**
167 When a multi-segment mbuf is freed, the field ``nb_seg`` is not reset
168 to 1 for the last segment of the chain. On next allocation of this segment,
H A Drelease_19_02.rst159 where segment the fd API is not expected to be supported:
161 - On attempt to get a segment fd for an externally allocated memory segment
162 - In cases where memfd support would have been required to provide segment
H A Drelease_2_1.rst578 * **fm10k: Fix TX multi-segment frame.**
918 Fixes issue where failing to allocate a segment, ``mlx4_rx_burst_sp()``
920 pointer in the last segment is not set.
H A Drelease_16_11.rst26 flag indicates that the segment size of original packets is known.
/dpdk/doc/guides/freebsd_gsg/
H A Dinstall_from_ports.rst97 EAL: Mapped memory segment 0 @ 0x1040000000: physaddr:0x180000000, len 1073741824
98 EAL: Mapped memory segment 1 @ 0x1080000000: physaddr:0x1c0000000, len 1073741824
/dpdk/doc/guides/sample_app_ug/
H A Dipv4_multicast.rst190 walk though all segments of the input packet and for each of segment,
191 create a new buffer and attach that new buffer to the segment
195 …roach does not make a clone, it just increments the reference counter for all input packet segment,
H A Dipsec_secgw.rst166 in other words maximum data size for one segment.
755 * Maximum segment size for TSO offload, available for egress SAs only.
761 * *mss N* N is the segment size in bytes
/dpdk/doc/guides/cryptodevs/
H A Doverview.rst28 outputting linear buffers (i.e. single segment).
H A Daesni_gcm.rst14 GMAC, however GMAC support is limited to one segment per operation. Please
/dpdk/doc/guides/tools/
H A Dtestregex.rst72 number of mbuf segment
H A Dcomp_perf.rst75 ``--seg-sz N``: size of segment to store the data (default: 2048)
H A Dcryptoperf.rst139 * ``--segment-sz <n>``
141 Set the size of the segment to use, for Scatter Gather List testing.
143 so a single segment is created.
/dpdk/doc/guides/howto/
H A Ddebug_troubleshoot.rst141 * If the drops occur for large size packets, check MTU and multi-segment
210 * Extra cycles to linearize multi-segment buffer and software offload like
/dpdk/doc/guides/testpmd_app_ug/
H A Drun_app.rst203 Enable scatter (multi-segment) RX.
392 Set TX segment sizes or total packet length. Valid for ``tx-only``
/dpdk/drivers/net/bnx2x/
H A Dbnx2x.h1882 bnx2x_igu_ack_sb_gen(struct bnx2x_softc *sc, uint8_t segment, in bnx2x_igu_ack_sb_gen() argument
1889 (segment << IGU_REGULAR_SEGMENT_ACCESS_SHIFT) | in bnx2x_igu_ack_sb_gen()

12