From: sabu kurian <sabu2kurian@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Intel DPDK drops packets in burst mode on I350
Date: Sat, 12 Apr 2014 14:33:46 +0530 [thread overview]
Message-ID: <CAJ2bnfAwz1YR-rs=p1vQ6yTs8a90FnP4VxXW=dXE=LyZ=n-JHA@mail.gmail.com> (raw)
I350 fails to sent packets in burst mode.
However it is possible to sent 1 packet at a time using the hardware.
I350 is being listed under the 'Supported NIC's' page on
http://dpdk.org/doc/nics
This is the code I used
ret = rte_eth_tx_burst(port_ids[lcore_id], 0, m_pool, burst_size);
If I give a burst_size of 1. It works fine.
When I set it to 64 or 128, it fails.
I have allocated packets using
struct rte_mbuf *m_pool[burst_size];
for(j=0;j<burst_size;j++)
{
m_pool[j] = rte_pktmbuf_alloc(pktmbuf_pool);
}
all the mbufs were set to have
m_pool->pkt.nb_segs = 1;
m_pool->pkt.next = NULL;
m_pool->pkt.pkt_len = (uint16_t)74;
m_pool->pkt.data_len = (uint16_t)74;
Where am I going wrong ? But the same code works perfectly inside a VM
Any help would be appreciated.
Thanks and Regards
reply other threads:[~2014-04-12 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJ2bnfAwz1YR-rs=p1vQ6yTs8a90FnP4VxXW=dXE=LyZ=n-JHA@mail.gmail.com' \
--to=sabu2kurian@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).