DPDK patches and discussions
 help / color / mirror / Atom feed
From: Perugu Hemasai Chandra Prasad <hemasaiperugu@5g.iith.ac.in>
To: users@dpdk.org, dev@dpdk.org
Subject: [dpdk-dev] Unable to receive packet size less than 60 with rte_eth_rx_burst Api - regarding
Date: Mon, 23 Sep 2019 14:14:21 +0530	[thread overview]
Message-ID: <CALJSgO77_LK=szQBJ9eSxg1fbmFErBoHp5LmW9N=5iHY8O_o2A@mail.gmail.com> (raw)

Hi All,
         when ever I am trying to send packets ( dpdk ver 18.05 stable ) of
size less than 60 bytes using rte_eth_tx_burst API with EthDev, packets are
receiving on other system with packet length of 60 bytes by appending
zeros's  to the end of the packet and there is no modification in the data.
But packet is receiving as it is without any appending of zero's when
packet size is more than 60. Is there any hidden limitation like this? can
anyone please tell me the reason ? How to resolve this ?

Thanks & Regards,
Hemasai

             reply	other threads:[~2019-09-23  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23  8:44 Perugu Hemasai Chandra Prasad [this message]
2019-09-23  9:52 ` Morten Brørup

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='CALJSgO77_LK=szQBJ9eSxg1fbmFErBoHp5LmW9N=5iHY8O_o2A@mail.gmail.com' \
    --to=hemasaiperugu@5g.iith.ac.in \
    --cc=dev@dpdk.org \
    --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).