DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ip_pipeline: add more functions to routing-pipeline
Date: Wed, 30 Sep 2015 15:38:13 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478DBD44@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1443626450-27607-1-git-send-email-jasvinder.singh@intel.com>



> -----Original Message-----
> From: Singh, Jasvinder
> Sent: Wednesday, September 30, 2015 4:21 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian
> Subject: [PATCH] ip_pipeline: add more functions to routing-pipeline
> 
> This patch adds following features to the
> routing-pipeline to enable it for various NFV
> use-cases;
> 
> 1.Fast-path ARP table enable/disable
> 2.Double-tagged VLAN (Q-in-Q) packet enacapsulation
> for the next-hop
> 3.MPLS encapsulation for the next-hop
> 4.Add colour (Traffic-class for QoS) to the MPLS tag
> 5.Classification action to select the input queue
> of the hierarchical scehdular (QoS)
> 

Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

  reply	other threads:[~2015-09-30 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 15:20 Jasvinder Singh
2015-09-30 15:38 ` Dumitrescu, Cristian [this message]
2015-10-01  9:05   ` [dpdk-dev] [PATCH v2] " Jasvinder Singh
2015-10-01  9:09     ` Dumitrescu, Cristian
2015-10-01 11:00     ` Neil Horman
2015-10-01 12:37       ` Dumitrescu, Cristian
2015-10-01 17:18         ` Neil Horman
2015-10-19 10:59           ` [dpdk-dev] [PATCH v3] " Jasvinder Singh
2015-10-28 10:35             ` [dpdk-dev] [PATCH v4] " Jasvinder Singh
2015-12-02 10:22               ` [dpdk-dev] [PATCH v5] " Jasvinder Singh
2015-12-07  0:55                 ` Thomas Monjalon

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=3EB4FA525960D640B5BDFFD6A3D89126478DBD44@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.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 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).