DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] Transmit Chained Buffers On mlx5
Date: Tue, 8 Oct 2019 14:35:07 -0700	[thread overview]
Message-ID: <CA+Gp1nbQ=__F60nAQaB9N2=GALjmJxmTQzXzixgMdw=Qp6AgWQ@mail.gmail.com> (raw)

Hi, I'm trying to figure out how to transmit a chained buffer, and I can't
find any examples or threads on this mailing list to do so. My assumptions
are:

1) Only the first mbuf contains the Ethernet and other packet headers, and
all the rest are essentially just appended to the end of that.
2) Once transmitted, the driver will construct all links of the chain into
a single jumboframe.
3) DEV_TX_OFFLOAD_MULTI_SEGS must be set in the TX offloads.

After setting up everything as above, I construct a chain of buffers using
rte_pktmbuf_chain. When I call rte_eth_tx_burst, it reports 1 packet sent
for the first packet with 2 segments, then 0 packets sent with packets
containing 20+ segments. Is there some limitation with chaining that I'm
hitting? It seems the maximum number of chains is set to UINT16_MAX in
DPDK, so 20 should be plenty small.

I'm using ConnectX-5/mlx with DPDK 19.05.

Thanks!

                 reply	other threads:[~2019-10-08 21:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CA+Gp1nbQ=__F60nAQaB9N2=GALjmJxmTQzXzixgMdw=Qp6AgWQ@mail.gmail.com' \
    --to=shaklee3@gmail.com \
    --cc=users@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).