From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f45.google.com (mail-it0-f45.google.com [209.85.214.45]) by dpdk.org (Postfix) with ESMTP id 01F181B280 for ; Thu, 21 Dec 2017 14:01:37 +0100 (CET) Received: by mail-it0-f45.google.com with SMTP id o130so14579650itg.0 for ; Thu, 21 Dec 2017 05:01:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=w1un+fqOga9TTej7rWjJUG3mLtXcCqqvrYT1wj0k7PE=; b=flFTYtdh4miPgLAP+MtC8qoVPYyru1JPmJCBBMFV3KTu/9VcT9UiLXlFmzlj5pEQ2Q VtxVJT3BuLzX6lgonWiaRkIPWs9o3BY+ogHqwIGvPCaokocE3YO4vGLidRTONvJdQHgY zrgDrG02k94V3MSVW3OFC7u2Tm9KokBjGpyZW6QRKvwIg+A9aOIf9IGPQ/M5CKjoP2eA Brsd9BpXGMdlgGqvz6AdO8HiShwquuV67Ff+O+iGZ9vaUVmRH8W/qjshoq41whHWSekn W+FpysMYKeYEj3GD/JRqBPurylun5M/h3qsAGbOHqqDBklmk068QQQiZslNxD96HUz2Y k/GQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=w1un+fqOga9TTej7rWjJUG3mLtXcCqqvrYT1wj0k7PE=; b=V2RjxY8phEKeOuU78Wj+EqnRczJb4tcSsu38Yr2AxPWT34ruqpUZVnX2WX96rVUTaK 9DSDZUgjErNIetjc3ZT18rR5WVgOxppjJknNyV+Gb02jc+wwK971GOMRtSLnc3AYsGz9 TAuJpSytLBod4jkLBbBxo0zWvUlCcjRJSekPAwqLOf2K44DvJYvMHiQikq5C38IFKc9w wQYkO55UkaAh4t73nSuxgBQMVRHNgxuNbk4W1quJvJaDBZ5QTxabBqxWlCQjp/oV/04d Mca+W0zvpD8zD9YcS8sFSX6SK/FTtcSSLd9WQ2ZE9BZbxUtI2A64reKEqO589dzKJo9J /Prw== X-Gm-Message-State: AKGB3mKAm2XnBKl8HmiO3SQA/HmYlXEYeZTIfjYtkxZb3oblGzBL2B03 RmIQ4I50mYQ1S2EafowiOXfpPfqHxxrPUD8vGr3JwtVx X-Google-Smtp-Source: ACJfBouS3/g7h+2/Y1jc7NA/GcjgPV3NeIFmZPFhGTAFG5W9ZgydA3r9L209SSf8S/V9nX90+SDv7L6NnBBl58J6d14= X-Received: by 10.36.39.8 with SMTP id g8mr13368040ita.42.1513861296988; Thu, 21 Dec 2017 05:01:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.53.2 with HTTP; Thu, 21 Dec 2017 05:01:36 -0800 (PST) In-Reply-To: <1513823719-36066-1-git-send-email-qi.z.zhang@intel.com> References: <1513823719-36066-1-git-send-email-qi.z.zhang@intel.com> From: Alex Rosenbaum Date: Thu, 21 Dec 2017 15:01:36 +0200 Message-ID: To: Qi Zhang Cc: adrien.mazarguil@6wind.com, DPDK , Declan Doherty Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC v2 0/5] rte_flow extension for vSwitch acceleration X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2017 13:01:38 -0000 On Thu, Dec 21, 2017 at 4:35 AM, Qi Zhang wrote: > This patch extend rte_flow API. > The purpose is to provide comfortable programming interface for virtual switch > software (such as OVS) to take advantage of incoming device's vSwitch acceleration > capability when using DPDK as data plane. > > Below is summary of changes: > > 1. Support to specify flow's destination as an ethdev interface. > > Add action RTE_FLOW_ACTION_TYPE_ETHDEV_PORT, use port_id as the identification > of the destitation. A typical use case is, with a smart NIC used for vSwitch > acceleration, flow is defined to redirect packet between switch port that is > managed by a Port Representor. > See patch for Port Representor: http://dpdk.org/dev/patchwork/patch/31458/ If we are going to have a representation of a switch in DPDK then I we need real PMD's for the switch ports, and not virtual PMD's as in the Port Representor model. These real ports will probably require specific switch_ops, which are different than the NIC (eth_dev_ops). At least few additional on top of NIC ops. We will need to support Tx and Rx burst on these switch ports and configure ACL's, flooding mode and more. Alex