From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2A628A0551; Mon, 17 Feb 2020 08:19:21 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 40A832C4F; Mon, 17 Feb 2020 08:19:20 +0100 (CET) Received: from mail-io1-f66.google.com (mail-io1-f66.google.com [209.85.166.66]) by dpdk.org (Postfix) with ESMTP id 8B8D21DBD; Mon, 17 Feb 2020 08:19:19 +0100 (CET) Received: by mail-io1-f66.google.com with SMTP id k24so4858860ioc.4; Sun, 16 Feb 2020 23:19:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=d8EkioS4BEp4+Va4k+lo2t29KoffBYyBSEVyjUN5A7M=; b=LTjJ148xcCYEJMdebmrb+t39lELTbzQN5QodGvaJ4hymU7OKz8lwGcTMJfFboYmH9P qzfTDLe78VsLEW+Os/tFWkJJtBt++Cmc6HGDsG9tyi7clfw2VHLXfrFZ7pBc/73sb7en qjd4UrtsdaCBXlodlNnmdVXou6DJqt2Y+ZKdLI9ezLJzIXI3nc6n3KoWqiYrr8pwAoNt oQRjG3o/ihSpii4vkNWNHcc13+k5YaRtJCGmMlkCuuLeOHGsXsQsbx+QWAI9kzktsCzB lSv3wNZHRQka0W3gEnTpf9q9QgyUdVFjb3H4LKDkwfSys6A9QGegekH/+GC7uqQ0J4h+ XluQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=d8EkioS4BEp4+Va4k+lo2t29KoffBYyBSEVyjUN5A7M=; b=e/2aIHROJ84joS3PGx7k+l/yfeRrr8zbXjV/9GwsF6taymn7qpn4QtKFg4MbMLExvc pR23BlTTKv+1JUm04Yfuzz4ZZB5AKOvJ8/nmu5Om222r+tZ0Z1nKdOIr2AetiVitfh8t GUIQNbbOyDvIByWUj/POHubSDfc5xoh3AM5vWnHHFvqbHvFl4kYcDHJFlDECW32vlmWz a7JBLBLCEdanhcT2rq2ljpa8YbvVnCveBjvsUQoTY4FqonT6q43NPFXod5iALMPAvDFd iLsEgp5XYhYYttyeTkMdhkh/JK6BQm9NTJvMBn3ZRmWRZ28IpbRnwZKkqe6aLpPwqEd1 eo3A== X-Gm-Message-State: APjAAAUoOXRLfEfCq5KlGDP8LOk3ilEpkucxXbINGxDmyDE6IGHf5E9c ZAN4Nvhr27CG83VWVtlAR5JEs/ubnL76z9z3Q8k= X-Google-Smtp-Source: APXvYqzzzMG1iGiQmB4onJwUpSEtf38KT2VsYZiamqYDlzqit4OsJ+8CjxYpR4qiyKy0blZr1JXv2H2KE/Czl6KfI9s= X-Received: by 2002:a6b:c742:: with SMTP id x63mr11157550iof.162.1581923958729; Sun, 16 Feb 2020 23:19:18 -0800 (PST) MIME-Version: 1.0 References: <20200131170201.3236153-1-jerinj@marvell.com> <76e12ab0-c467-986f-dac3-6e896f3fb193@ashroe.eu> In-Reply-To: From: Jerin Jacob Date: Mon, 17 Feb 2020 12:49:02 +0530 Message-ID: To: Ray Kinsella Cc: Jerin Jacob , dpdk-dev , Prasun Kapoor , Nithin Dabilpuram , Kiran Kumar K , Pavan Nikhilesh , Narayana Prasad , nsaxena@marvell.com, sshankarnara@marvell.com, Honnappa Nagarahalli , Thomas Monjalon , David Marchand , Ferruh Yigit , Andrew Rybchenko , Ajit Khaparde , "Ye, Xiaolong" , Raslan Darawsheh , Maxime Coquelin , Akhil Goyal , Cristian Dumitrescu , John McNamara , "Richardson, Bruce" , Anatoly Burakov , Gavin Hu , David Christensen , "Ananyev, Konstantin" , Pallavi Kadam , Olivier Matz , Gage Eads , "Rao, Nikhil" , Erik Gabriel Carrillo , Hemant Agrawal , "Artem V. Andreev" , Stephen Hemminger , Shahaf Shuler , "Wiles, Keith" , =?UTF-8?Q?Mattias_R=C3=B6nnblom?= , Jasvinder Singh , Vladimir Medvedkin , techboard@dpdk.org, Stephen Hemminger , dave@barachs.net Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC PATCH 0/5] graph: introduce graph subsystem 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I got initial comments from Ray and Stephen on this RFC[1]. Thanks for the comments. Is anyone else planning to have an architecture level or API usage level review or any review of other top-level aspects? I believe low-level aspects of the code can be taken care of from the v1 series onwards. I am just wondering what would be an appropriate time for sending v1. If someone planning for reviewing at the top level, I can wait until the review complete. Let us know if anyone planning to review? If no other comment then I would like to request tech board approval for the library on 26/Feb meeting. [1] http://mails.dpdk.org/archives/dev/2020-January/156765.html On Sat, Feb 1, 2020 at 11:14 AM Jerin Jacob wrote: > > On Sat, Feb 1, 2020 at 12:05 AM Ray Kinsella wrote: > > > > Hi Jerin, > > Hi Ray, > > > Much kudos on a huge contribution to the community. > > All the authors of this patch set spend at least the last 3/4 months > to bring this up RFC with performance data with an l3fwd-graph example > application. > We hope it would be useful for DPDK community. > > > Look forward to spend more time looking at it in the next few days. > > That would be very helpful. > > > > > I'll bite and ask the obvious questions - why would I use rte_graph over FD.io VPP? > > I did not get the opportunity to work day to day on FD.io projects. My > understanding of FD.io is very limited. > I do think, it is NOT one vs other. VPP is quite a mature project and > they are pioneers in graph architecture. > > VPP is an entirely separate framework by itself and provides an > alternate data plane environment. > The objective of rte_graph is to add a graph subsystem to DPDK as a > foundational element. > This will allow the DPDK community to use the powerfull graph > architecture concept in a fundamental > way with purely DPDK based applications > > That would boil down to: > 1) Provision to use pure native mbuf based dpdk application with graph > architecture. i.e > avoid the cost of packet format conversion for good. > 2) Use rte_mempool, rte_flow, rte_tm, rte_cryptodev, rte_eventdev, > rte_regexdev HW accelerated > API in the data plane application. > 3) Based on our experience, NPU HW accelerates are so different than > one vendor to another vendor. > Going forward, We believe, API abstraction may not be enough abstract > the difference in HW. > The Vendor-specific nodes can abstract the HW differences and reuse > generic the nodes as needed. > This would help both the silicon vendors and DPDK end-users to avoid writing > capabilities based APIs and avoid vendor-specific fast path routines. > So such vendor plugin can be part of dpdk to help both vendors > and end-user of DPDK. > 4) Provision for multiprocess support in graph architecture. > 5) Contribute to dpdk.org > 6) Use Linux coding standards. > 7) Finally, one may consider using rte_graph, _if_ specific workload > performs better in performance > in this model due to framework and/or the HW acceleration attached to it. > > > > > > Ray K > >