From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Sam <batmanustc@gmail.com>, keith.wiles@intel.com
Cc: mb@smartsharesystems.com, dev@dpdk.org
Subject: Re: [dpdk-dev] Where is the padding code in DPDK?
Date: Thu, 15 Nov 2018 10:06:36 +0000 [thread overview]
Message-ID: <e6b8853e-d523-9e9f-3ed9-e6eb0c51aa62@intel.com> (raw)
In-Reply-To: <CAOE=1Z36qgkV3NLF3z49oLSv8jif7gx9Wjd54qomJipcP1-6Ow@mail.gmail.com>
On 15-Nov-18 2:07 AM, Sam wrote:
> So, to be brief, rte_eth_rx_burst and rte_eth_tx_burst, just send mbuf,
> will not do anything.
> Is that right?
>
You're trying to arrive at certainty where there is none.
The *API* will not do anything. The NIC itself might, depending on
specifics of the hardware.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-11-15 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 7:16 Sam
2018-11-13 7:17 ` Sam
2018-11-13 7:22 ` Sam
2018-11-13 9:29 ` Burakov, Anatoly
2018-11-14 5:45 ` Sam
2018-11-14 10:17 ` Burakov, Anatoly
2018-11-14 10:51 ` Morten Brørup
2018-11-14 16:19 ` Wiles, Keith
2018-11-15 2:07 ` Sam
2018-11-15 2:13 ` Sam
2018-11-15 10:06 ` Burakov, Anatoly [this message]
2018-11-15 10:27 ` Morten Brørup
2018-11-15 13:32 ` Wiles, Keith
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=e6b8853e-d523-9e9f-3ed9-e6eb0c51aa62@intel.com \
--to=anatoly.burakov@intel.com \
--cc=batmanustc@gmail.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=mb@smartsharesystems.com \
/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).