All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4] ip_pipeline: add flow id parameter to flow classification
Date: Mon, 07 Dec 2015 01:50:41 +0100	[thread overview]
Message-ID: <3140911.8Sfk5dHe2S@xps13> (raw)
In-Reply-To: <1448892502-32092-1-git-send-email-jasvinder.singh@intel.com>

2015-11-30 14:08, Jasvinder Singh:
> This patch adds flow id field to the flow
> classification table entries and adds table action
> handlers to read flow id from table entry and
> write it into the packet meta-data. The flow_id
> (32-bit) parameter is also added to CLI commands
> flow add, flow delete, etc.
> 
> *v2
> fixed bug: flow table entry size power of 2
> 
> *v3
> fixed bug: changed LRU hash table operation to
> extendible bucket hash table operation
> 
> *v4
> Coverity issue: 120147
> Fixes: 7122d30131ad ("examples/ip_pipeline: rework flow classification
> pipeline")
> 
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks

      reply	other threads:[~2015-12-07  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 11:13 [PATCH v2] ip_pipeline: add flow id parameter to flow classification Jasvinder Singh
2015-10-05 13:10 ` Dumitrescu, Cristian
2015-10-12 15:41 ` [PATCH v3] " Jasvinder Singh
2015-10-12 15:46   ` Dumitrescu, Cristian
2015-10-12 15:51     ` Singh, Jasvinder
2015-11-30 14:08 ` [PATCH v4] " Jasvinder Singh
2015-12-07  0:50   ` Thomas Monjalon [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=3140911.8Sfk5dHe2S@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    /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.