From: Ansar Kannankattil <ansarkannankat@gmail.com>
To: dev@dpdk.org
Subject: Can I use rte_pktmbuf_chain to chain multiple mbuffs for calling only single tx_eth_burst API
Date: Wed, 9 Feb 2022 23:33:13 +0530 [thread overview]
Message-ID: <CAPA_rBexb_JKhGtxp4uQ1M-5F0RXpvpOHxDCso5VxmjRxkL1eA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Hi
My intention is to decrease the number of rte_tx_eth_burst calls, I know
that mentioning nb_pkts will result in sending multiple packets in a single
call.
But providing nb_pkts=1 and posting a head mbuff having number of
mbuffs linked with it will results sending multiple packets
If not, what is the use case of linking multiple mbuffs together
[-- Attachment #2: Type: text/html, Size: 406 bytes --]
next reply other threads:[~2022-02-09 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 18:03 Ansar Kannankattil [this message]
2022-02-09 20:56 ` Stephen Hemminger
2022-02-09 22:18 ` Ferruh Yigit
2022-02-09 22:46 ` Stephen Hemminger
2022-02-10 8:56 ` Ferruh Yigit
2022-02-10 10:37 ` Ansar Kannankattil
2022-02-10 10:43 ` Ferruh Yigit
2022-02-10 11:36 ` Bruce Richardson
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=CAPA_rBexb_JKhGtxp4uQ1M-5F0RXpvpOHxDCso5VxmjRxkL1eA@mail.gmail.com \
--to=ansarkannankat@gmail.com \
--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).