From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Where is the padding code in DPDK?
Date: Tue, 13 Nov 2018 15:22:28 +0800 [thread overview]
Message-ID: <CAOE=1Z1rwCU5PavwdScSR=wBkZh_rE5s=h0r8B_m0b560R7bUw@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z05+OJVU5AxMdH1LfBhHk0JSpQ9LvsFFuPZwjyFMKGAVA@mail.gmail.com>
And what about rte_vhost_user_rx_burst and rte_vhost_user_tx_burst
Sam <batmanustc@gmail.com> 于2018年11月13日周二 下午3:17写道：
> And what about vhost-user port?
>
> Sam <batmanustc@gmail.com> 于2018年11月13日周二 下午3:16写道：
>
>> Hi all,
>>
>> As we know, ethernet frame must longer then 64B.
>>
>> So if I create rte_mbuf and fill it with just 60B data, will
>> rte_eth_tx_burst add padding data, let the frame longer then 64B
>>
>> If it does, where is the code?
>>
>
next prev parent reply other threads:[~2018-11-13 7:22 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 [this message]
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
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='CAOE=1Z1rwCU5PavwdScSR=wBkZh_rE5s=h0r8B_m0b560R7bUw@mail.gmail.com' \
--to=batmanustc@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).