DPDK usage discussions
 help / color / mirror / Atom feed
From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>
Cc: users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Defining multiple actions based on a field value for the same table lookup in ip_pipeline application
Date: Fri, 19 May 2017 11:07:35 +0530	[thread overview]
Message-ID: <CAGSp03=Obw9pF5XHtsECODJdRzvMYwfZ5fqoUKLwqqDP5-itOQ@mail.gmail.com> (raw)
In-Reply-To: <CAAx9ALVxRHAA3RvG21LmYCnJk_S8j9PvbrdHZ5W8z9TBZCbNZg@mail.gmail.com>

That can be done in the same miss function as I understand, if (condition1)
{} else {}

On Fri, May 19, 2017 at 10:53 AM, Nidhia Varghese <
nidhiavarghese93@gmail.com> wrote:

> Thanks for your reply Shyam.
> Yes, I went through it. But my doubt is whether it is possible to define
> two different miss actions based on some decision criteria(input port in my
> case).
> Miss ->Case 1: Add entry to table if portid = 1
>         ->Case 2: Drop if portid = 2
>
> On Thu, May 18, 2017 at 7:34 PM, Shyam Shrivastav <
> shrivastav.shyam@gmail.com> wrote:
>
>> For each table a lookup hit and miss function can be registered, have a
>> look at
>> rte_pipeline_run(struct rte_pipeline *p) for the semantics
>>
>
> Thanks,
> Nidhia Varghese
>

  reply	other threads:[~2017-05-19  5:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 12:23 [dpdk-users] " Nidhia Varghese
2017-05-18 14:04 ` [dpdk-users] [dpdk-dev] " Shyam Shrivastav
2017-05-19  5:23   ` Nidhia Varghese
2017-05-19  5:37     ` Shyam Shrivastav [this message]
2017-07-17  2:03   ` [dpdk-users] Rx Can't receive anymore packet after received 1.5 billion packet vuonglv
2017-07-17 10:31     ` [dpdk-users] [dpdk-dev] " Dumitrescu, Cristian
2017-07-18  1:36       ` vuonglv
2017-07-19 18:43         ` Dumitrescu, Cristian
2017-07-21 10:49           ` vuonglv

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='CAGSp03=Obw9pF5XHtsECODJdRzvMYwfZ5fqoUKLwqqDP5-itOQ@mail.gmail.com' \
    --to=shrivastav.shyam@gmail.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).