DPDK patches and discussions
 help / color / mirror / Atom feed
From: sabu kurian <sabu2kurian@gmail.com>
To: Chae-yong Chong <cychong@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] I350 drops packet on rte_eth_tx_burst()
Date: Sun, 13 Apr 2014 11:38:52 +0530	[thread overview]
Message-ID: <CAJ2bnfC8m2w3ZfEqvsvLxm5a+3E45JjvsDTAztvROwLeLhvdNQ@mail.gmail.com> (raw)
In-Reply-To: <65072E01-9F4F-4C35-A173-2299B5C6CE0D@gmail.com>

Hai  Chae-yong Chong,

Thanks on the reply.

But I'm nor actually forwarding packets. I'm crafting my own packets in
mbuf's (74 byte packets all)
and sending it using
ret = rte_eth_tx_burst(port_ids[lcore_id], 0, m_pool,burst_size);

When burst_size is 1, it does work. Work in the sense the NIC will continue
with sending packets, at a little over
50 percent of the link rate. For 1000 Mbps link rate .....The observed
transmit rate of the NIC is 580 Mbps (using Intel DPDK).
When the NIC sends out some hundred thousand packets , billions are getting
dropped as well. I don't care about the billions getting
dropped, but it should be possible to achieve at least 900 Mbps transmit
rate with Intel DPDK and I350 on 1 Gbps link.

Could someone help me out on this ?

Thanks and regards


On Sun, Apr 13, 2014 at 10:44 AM, Chae-yong Chong <cychong@gmail.com> wrote:

> I think if you just forward the packets there should be no tx failure. If
> you instruct the core to send the packet in burst, the tx rate is higher
> than 10Gbps as the core is too powerful.
>
> ---
> Sent from Boxer | http://getboxer.com <http://bit.ly/1hRkK2W>
> On April 11, 2014 at 7:16:47 PM GMT+9, sabu kurian <sabu2kurian@gmail.com>
> wrote:
>
> To add to my previous mail.....
>
> only upto 544 packets are actually sent... then it fails
>
>
> On Fri, Apr 11, 2014 at 3:34 PM, sabu kurian  wrote:
>
> > Hi Friends,
> >
> > Thanks for the reply.
> >
> > This is the portion of the code where the I350 fails to send packet:
> >
> > for(;;){
> >
> > ret = rte_eth_tx_burst(port_ids[lcore_id], 0, m_pool,
> > burst_size);
> >
> > if (unlikely(ret < burst_size)) {
> > for(j=ret;j<(burst_size-ret);j++)
> > {
> > rte_pktmbuf_free(m_pool[j]);
> > }
> > }
> > else
> > {
> >
> > lcore_stats[lcore_id].tx += (uint64_t)burst_size;
> > }
> >
> > }
> >
> > all of the m_pool were allocated using
> >
> > for(j=0;j> {
>
> > m_pool[j] = rte_pktmbuf_alloc(pktmbuf_pool);
> >
> > }
> >
> >
> >
> >
> > On Fri, Apr 11, 2014 at 1:26 PM, Thomas Monjalon <
> > thomas.monjalon@6wind.com> wrote:
> >
> >> Hi,
> >>
> >> 2014-04-11 11:29, sabu kurian:
> >> > Even after installing all the required igb drivers for I350 (the
> device
> >> > seems to work perfect on the host machine), am unable to transmit
> >> packets
> >> > using the same device (on Intel DPDK) using
> >>
> >> Please follow this documentation to setup your environment and do some
> >> basic
> >> tests with testpmd:
> >> http://dpdk.org/doc/quick-start
> >>
> >> --
> >> Thomas
> >>
> >
> >
>
>

      reply	other threads:[~2014-04-13  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  5:59 sabu kurian
2014-04-11  7:56 ` Thomas Monjalon
2014-04-11 10:04   ` sabu kurian
2014-04-11 10:04     ` sabu kurian
2014-04-13  5:14       ` Chae-yong Chong
2014-04-13  6:08         ` sabu kurian [this message]

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=CAJ2bnfC8m2w3ZfEqvsvLxm5a+3E45JjvsDTAztvROwLeLhvdNQ@mail.gmail.com \
    --to=sabu2kurian@gmail.com \
    --cc=cychong@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).