DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Getting meta data from different pipelines in ip_pipeline application
Date: Wed, 7 Jun 2017 17:08:07 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA65F02@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAAx9ALX5bX5pQCLUxRqb-thdhOvdJwdAwahqiGPtrzWBUoQ6GA@mail.gmail.com>

If you print the bytes of the key read by the flow classification pipeline, is it as expected? Make sure you don’t have bytes of random data (incorrect masks) or endianess issues.

From: Nidhia Varghese [mailto:nidhiavarghese93@gmail.com]
Sent: Sunday, June 4, 2017 8:20 AM
To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Cc: users@dpdk.org; dev@dpdk.org
Subject: Re: [dpdk-dev] Getting meta data from different pipelines in ip_pipeline application

Hi,

I tested it, but its not working as expected.

Pipelines 4,5 and 6 are passthrough pipelines and 7 is of flow classification type. Packets are getting dropped at pipeline 7.

On Sat, Jun 3, 2017 at 6:01 PM, Dumitrescu, Cristian <cristian.dumitrescu@intel.com<mailto:cristian.dumitrescu@intel.com>> wrote:
Hi Nidhia,

You should go ahead and test it. Did you test it and it did not work as you expect?

Personally, I cannot see any reasons why it should not work, but you need to test it yourself. I am assuming that pipelines 4, 5,6 below have the passthrough type and pipeline 7 has the flow classification type.

Regards,
Cristian


Regards,
Nidhia Varghese

      reply	other threads:[~2017-06-07 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  7:03 Nidhia Varghese
2017-06-01 12:58 ` Nidhia Varghese
2017-06-03 12:31   ` Dumitrescu, Cristian
2017-06-04  7:20     ` Nidhia Varghese
2017-06-07 17:08       ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D891267BA65F02@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=nidhiavarghese93@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).