From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nikita Kozlov <nikita@gandi.net>
Subject: Release of Packet Journey
Date: Thu, 29 Oct 2015 20:53:41 +0100
Message-ID: <56327945.3090804@gandi.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from gandi.net (mail4.gandi.net [217.70.183.210])
 by dpdk.org (Postfix) with ESMTP id 1A5AA8DA2
 for <dev@dpdk.org>; Thu, 29 Oct 2015 20:53:44 +0100 (CET)
Received: from mfiltercorp2.gandi.net (mfiltercorp2.gandi.net [217.70.183.154])
 by gandi.net (Postfix) with ESMTP id 0A21DE3A4D
 for <dev@dpdk.org>; Thu, 29 Oct 2015 20:53:44 +0100 (CET)
Received: from gandi.net ([IPv6:::ffff:217.70.183.210])
 by mfiltercorp2.gandi.net (mfiltercorp2.gandi.net [::ffff:217.70.183.154])
 (amavisd-new, port 10024)
 with ESMTP id mu5iLF-XdWeI for <dev@dpdk.org>;
 Thu, 29 Oct 2015 20:53:43 +0100 (CET)
Received: from [10.242.8.14] (fob.gandi.net [217.70.181.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by gandi.net (Postfix) with ESMTPSA id C5518E3A4B
 for <dev@dpdk.org>; Thu, 29 Oct 2015 20:53:42 +0100 (CET)
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hello,

We have opensourced our dpdk-based project, Packet Journey
https://github.com/Gandi/packet-journey .

Packet Journey is a combinationof Linux RT_NETLINK and severalparts
ofDPDK (rte_kni, rte_lpm, rte_acl, rte_cmdline) and is intended to
serveas an edge router.

Our use case is:
- pktj starts several forwarding threads and a KNI thread per external port
- pktj launches a script which configures the KNI interface (MAC, IP,
VLAN) and launches a BGP daemon
- the host receives routes from the BGP daemon
- the BGP daemon injects the routes in Linux
- pktj receives the routes from NETLINK and put them in LPM in our
"control" threads
- pktj forwards packets to the KNI if the packets are
  - for the KNI IP or
  - if the neighbor is not known yet
  - if ttl reaches 0
- pktj filters packets if they match an ACLor if they exceed the rate
limit, kni output is also rate-limited
- pktj forwards packetsdirectly from the RXqueue to the TXqueue if the
neighbor is known

-- 
Nikita