From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail04.ics.ntt-tx.co.jp (mail05.ics.ntt-tx.co.jp [210.232.35.69]) by dpdk.org (Postfix) with ESMTP id F33061B680 for ; Mon, 25 Dec 2017 05:42:19 +0100 (CET) Received: from gwchk03.silk.ntt-tx.co.jp (gwchk03.silk.ntt-tx.co.jp [10.107.0.111]) by mail04.ics.ntt-tx.co.jp (unknown) with ESMTP id vBP4gG1I031313 for unknown; Mon, 25 Dec 2017 13:42:16 +0900 Received: (from root@localhost) by gwchk03.silk.ntt-tx.co.jp (unknown) id vBP4gGGJ001747 for unknown; Mon, 25 Dec 2017 13:42:16 +0900 Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] by gwchk03.silk.ntt-tx.co.jp with ESMTP id PAA01746; Mon, 25 Dec 2017 13:42:16 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by ccmail04.silk.ntt-tx.co.jp (unknown) with ESMTP id vBP4gGjd010532 for unknown; Mon, 25 Dec 2017 13:42:16 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by imss06.silk.ntt-tx.co.jp (unknown) with ESMTP id vBP4gGkO020780 for unknown; Mon, 25 Dec 2017 13:42:16 +0900 Received: from ccmail04 (smtp03.silk.ntt-tx.co.jp [10.107.0.135]) by imss06.silk.ntt-tx.co.jp (unknown) with SMTP id vBP4gGXg020777 for unknown; Mon, 25 Dec 2017 13:42:16 +0900 Date: Mon, 25 Dec 2017 13:41:48 +0900 From: Nakamura Hioryuki MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.73 [ja] X-CCMail7: CC-Mail-V7.0.2-Client-Relayed Message-Id: <201712250441.vBP4fm8D010099@ccmail04.silk.ntt-tx.co.jp> X-TM-AS-MML: No X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server To: spp@dpdk.org Subject: [spp] Proposal - spp_vf(SR-IOV like feature) addition to SPP X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Dec 2017 04:42:20 -0000 Hi everyone, As announced in DPDK Summit, we would like to introduce a SR-IOV like network functionality to SPP on DPDK17.08[1]. To support such functionality, we have developed new controller(spp_vf.py) and secondary process(spp_vf). spp_vf process has three kinds of component, classifier, forwarder and merger. These components communicate each other via ring-pmd, and provides SR-IOV like packet classification function according to virtual MAC address. Classifier: This component provides packet forwarding function from one port to one port. Classifier has table of virtual MAC address. According to this table, classifier lookups L2 destination MAC address and determines which port to be transferred to incoming packets. L2 Multicast feature is also supported. Forwarder: This provides function for packet processing from one port to one port. Incoming packets from port are to be transferred to specific one port. The direction of this transferring is specified by `port` command. Merger: This component provides packet forwarding function from multiple ports to one port. Incoming packets from multiple ports are to be transferred to one specific port. The flow of this merging process is specified by `port` command. By the combination of these component, following SR-IOV like function can be configured. +----------+ +-----------+ |Classifier|->ringPMD->|Forwarder#1|->vhost->VM#1 --------+ Packet(dstMAC:A/B) | | +-----------+ (vMAC:A) | ------phy--------> | | +-----------+ | | |->ringPMD->|Forwarder#2|->vhost->VM#2 ---+ | | | +-----------+ (vMAC:B)| | +----------+ | | | | +----------+ +-----------+ | | |Merger |<-ringPMD<-|Forwarder#3|<-vhost --==----------+ | | +-----------+ | <------phy--------| | +-----------+ | | |<-ringPMD<-|Forwarder#4|<-vhost ---------+ +----------+ +-----------+ Limitaion#1: vlan support is not yet, this feature is in still our backlogs. Limitaion#2: Support DPDK17.11 is not yet. Code changes will be posted in the following emails. Regard, -- Hiroyuki Nakamura NTT TechnoCross Corporation