All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tetsuya.Mukawa" <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
To: Meir Tseitlin <mirots-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Weird behavior of DPDK - ongoing problem
Date: Mon, 14 Apr 2014 16:20:50 +0900	[thread overview]
Message-ID: <534B8C52.8070003@igel.co.jp> (raw)
In-Reply-To: <CA+Typ9mstsAQEHaYCAa39gKY9EHObkzeTXcav_5s9Gr5xNY7xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Meir,

(2014/04/13 19:21), Meir Tseitlin wrote:
> The problem is that in 30% of the cases data packet enters the path of
> control packet instead of expected answer. Which probably means that after
> my packet type check, the mbuf is overwritten before handled properly.
If you are using DPDK-1.5, it's nice to update to DPDK-1.6, because pcap
pmd of DPDK-1.5 has buffer overflow while receiving  data from a target
device/file. And the issue was solved with DPDK-1.6 (in both intel
original code and dpdk.org code).

Also if multiple processes/threads run on a same cpu, probably, it could
cause a problem like you're facing.

Regards,
Tetsuya

  parent reply	other threads:[~2014-04-14  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 10:21 Weird behavior of DPDK - ongoing problem Meir Tseitlin
     [not found] ` <CA+Typ9mstsAQEHaYCAa39gKY9EHObkzeTXcav_5s9Gr5xNY7xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-14  7:20   ` Tetsuya.Mukawa [this message]
     [not found]     ` <534B8C52.8070003-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2014-04-14  7:46       ` Meir Tseitlin

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=534B8C52.8070003@igel.co.jp \
    --to=mukawa-alsx/un32fvpdbfq/vqriq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=mirots-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.