DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry B <dimsol@gmail.com>
To: maverickjin88@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] stalled after receiving 8000 rte_mbuf (4096 byte)
Date: Mon, 13 Aug 2018 09:48:43 +0300	[thread overview]
Message-ID: <CA+SXr77xLrNJ5+Q3jfe6qu062PfGq_rDrGo+-BB8OcbCq39PUQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8vx=jp-uJtO-2pFi+8tKa9e4hua+Hqo2oRaFUWCpmO=F4aMA@mail.gmail.com>

Hi,

Is there a chance you don't free mbufs (*rte_pktmbuf_free()*)?

Thanks
Dima

On Mon, Aug 13, 2018 at 6:35 AM Sungho Hong <maverickjin88@gmail.com> wrote:

> Hello
>
> I am developing a project with DPDK but have encountered a silly issue,
> that is not obvious to me.
>
> I am sending and receiving 4kb rte_mbuf between remote and local node,
> that alone works fine,
> however when I combine the implemenation with 3rd party library, the DPDK
> stops receiving the data after approximatelyr receiving 8000 packets.
>
> I have debugged all the possible program side and to my astonishement.
> there is no error found and all the packets that are within 8000 are
> received correctly.
>
> I have  no idea the approach to find out the problem of this situation. but
> the situation that I have mentioned can be replicated. It always stops at
> approximately 8000 packets received.
> and there are absolutely no bugs found in dpdk (user interface). The only
> problem is the rte_rx_queue stops returning the packets after 8000 packets.
>
> Would there be a good approach to identify the problem of this case?
>


-- 
-----

  reply	other threads:[~2018-08-13  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  3:35 Sungho Hong
2018-08-13  6:48 ` Dmitry B [this message]
2018-08-13 19:57   ` Sungho Hong

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=CA+SXr77xLrNJ5+Q3jfe6qu062PfGq_rDrGo+-BB8OcbCq39PUQ@mail.gmail.com \
    --to=dimsol@gmail.com \
    --cc=maverickjin88@gmail.com \
    --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).