DPDK patches and discussions
 help / color / mirror / Atom feed
From: Prashant Upadhyaya <praupadhyaya@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Packet Rx issue with DPDK1.8
Date: Thu, 8 Jan 2015 13:40:54 +0530	[thread overview]
Message-ID: <CAPBAu3UCua6QWpJnhpJ7nkPBvjbN5b88iTD1ZAh+DfY9Eb6BFA@mail.gmail.com> (raw)

Hi,

I am migrating from DPDK1.7 to DPDK1.8.
My application works fine with DPDK1.7.
I am using 10 Gb Intel 82599 NIC.
I have jumbo frames enabled, with max_rx_pkt_len = 10232
My mbuf dataroom size is 2048+headroom
So naturally the ixgbe_recv_scattered_pkts driver function is triggered for
receiving.
This works with DPDK1.7 and my app receives packets.
However, it does not work with DPDK1.8 somehow.I don't receive any packets.

So, I increased the mbuf data room size in my application to a higher value
so that the function ixgbe_recv_scattered_pkts is not enabled (I believe
ixgbe_recv_pkts will be used in this case), and now my application starts
getting packets with DPDK1.8 and the entire application usecase works fine
(ofcourse my application had to adapt to the mbuf structure changes which I
have done)

I am kind of coming to the conclusion that ixgbe_recv_scattered_pkts has
something broken in DPDK1.8 as compared to the earlier versions by the
above empirical evidence.

Has anybody else faced a similar issue ?

Regards
-Prashant

             reply	other threads:[~2015-01-08  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  8:10 Prashant Upadhyaya [this message]
2015-01-08 13:47 ` Bruce Richardson
2015-01-09  6:45   ` Prashant Upadhyaya
2015-01-09  9:26     ` Bruce Richardson
2015-01-14 16:30       ` Thomas Monjalon
2015-01-14 17:01         ` Bruce Richardson
2015-01-14 18:33         ` [dpdk-dev] New to DPDK Ravi Rao
2015-01-14 19:27           ` Wiles, Keith
2015-01-14 19:54             ` Ravi Rao
     [not found]               ` <D0DC2CB2.FCE3%keith.wiles@intel.com>
2015-01-21 21:00                 ` Ravi Rao

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=CAPBAu3UCua6QWpJnhpJ7nkPBvjbN5b88iTD1ZAh+DfY9Eb6BFA@mail.gmail.com \
    --to=praupadhyaya@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).