DPDK usage discussions
 help / color / mirror / Atom feed
From: Yuliang Li <yuliang.li@yale.edu>
To: users@dpdk.org
Subject: [dpdk-users] difference between rte_eth_tx_buffer and rte_eth_tx_burst
Date: Sat, 4 Mar 2017 20:46:23 -0500	[thread overview]
Message-ID: <CAECc8jop=DtPm8WbAsgEA2J34rxPSCXWzCoWk9ASznRoG55iQA@mail.gmail.com> (raw)

Hi all,

I am new to DPDK. I found 2 functions that can send packets:
rte_eth_tx_buffer and rte_eth_tx_burst. I am confused about why we need
these two different functions. To me, I can use only rte_eth_tx_burst, and
rte_eth_tx_buffer does add more functional capability. Are there any other
concerns like performance or others that we need these two functions?

Thanks,
-- 
Yuliang Li
PhD student
Department of Computer Science
Yale University

             reply	other threads:[~2017-03-05  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05  1:46 Yuliang Li [this message]
2017-03-05 15:22 ` Wiles, Keith
2017-03-05 17:26   ` Yuliang Li
2017-03-06  9:17   ` Thomas Monjalon

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='CAECc8jop=DtPm8WbAsgEA2J34rxPSCXWzCoWk9ASznRoG55iQA@mail.gmail.com' \
    --to=yuliang.li@yale.edu \
    --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).