From: Yuliang Li <yuliang.li@yale.edu>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] difference between rte_eth_tx_buffer and rte_eth_tx_burst
Date: Sun, 5 Mar 2017 12:26:47 -0500 [thread overview]
Message-ID: <CAECc8jr=Y-HTUs2bt-RdOae=W2exVpf+G3QVDkfR9rHNJLOFWQ@mail.gmail.com> (raw)
In-Reply-To: <A540AE91-1095-4F2C-934F-3155C142D2C2@intel.com>
Thanks Keith. This is very helpful!
On Sun, Mar 5, 2017 at 10:22 AM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
> > On Mar 4, 2017, at 7:46 PM, Yuliang Li <yuliang.li@yale.edu> wrote:
> >
> > 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?
>
> The best place to find out this type of information is to read the emails
> around the rte_eth_tx_buffer APIs in the archives. You may want to refine
> the search.
>
> https://mail-archive.com/search?a=1&l=dev%40dpdk.org&o=
> newest&haswords=rte_eth_tx_buffer
>
> >
> > Thanks,
> > --
> > Yuliang Li
> > PhD student
> > Department of Computer Science
> > Yale University
>
> Regards,
> Keith
>
>
--
Yuliang Li
PhD student
Department of Computer Science
Yale University
next prev parent reply other threads:[~2017-03-05 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 1:46 Yuliang Li
2017-03-05 15:22 ` Wiles, Keith
2017-03-05 17:26 ` Yuliang Li [this message]
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='CAECc8jr=Y-HTUs2bt-RdOae=W2exVpf+G3QVDkfR9rHNJLOFWQ@mail.gmail.com' \
--to=yuliang.li@yale.edu \
--cc=keith.wiles@intel.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).