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 C067FA0350; Tue, 23 Jun 2020 16:51:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9C8211D687; Tue, 23 Jun 2020 16:51:54 +0200 (CEST) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id C38861D675 for ; Tue, 23 Jun 2020 16:51:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592923913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=my5WBPYv98jPecNIvdchjSxUAiVUuPJD6iJsD8cMFtE=; b=AnRJptQt2EL7g33hd33V/yjpVa3yvCI4eoJOhkhRLG31iD1w5Tu8oyeKCuPeTwC9N6TtqU Hvf5AwXPf42QGHKEecMfhDGfM/oR0e1MheKTbqxE2sfgoJIJtjuqACg87rFhGFk9W/X1Wu FsVYUiGHqC3DodgpTkMCs9QiW1P8tVs= Received: from mail-vk1-f198.google.com (mail-vk1-f198.google.com [209.85.221.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-168-4iyvVGTKMVWmB3CVH772vA-1; Tue, 23 Jun 2020 10:51:49 -0400 X-MC-Unique: 4iyvVGTKMVWmB3CVH772vA-1 Received: by mail-vk1-f198.google.com with SMTP id r123so6090351vkg.3 for ; Tue, 23 Jun 2020 07:51:49 -0700 (PDT) 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=my5WBPYv98jPecNIvdchjSxUAiVUuPJD6iJsD8cMFtE=; b=frkS8OQ4W6FCOUBBSy3D16aPTDAItQJoQ/QA0L8B7j9KOjShg/0/B+npNVPb+p1O5d WYUlzZ3qBbrq4ztol+6hhsxKvWFa8Xmp+GumtaQE9t3khmnWIVNVJ/UCQ4mvB6NEPJuA fQE14jSY25Nfyv/trc16SGvQ2fJKxxdETaEcHQbpqApyfpzJgloEWsUy/SBWUAKmpkAF +LGQADtjVhSKmefLghwtymfFQznxe2d3Cz9CHjMHhUM4g2o1Byih9jlTz59yy8Xag5YU fDRC7ZcdVhWi7dub3NRnynp4tqHGVLyVI/sbZQst0skB7jf+yhJhKn7jF3qYNjXlusDI 0ppA== X-Gm-Message-State: AOAM5330auIFNG46wZfxlbPiSE9yxI25owgWWiKG5LDwD8IyGAGFGtZN wgrcL6O7heC/Ngu6lcV/3ObWlmkAvp0iL9tLXiBvN02u5xT3KR73+NPJ1kLTvGl6/9biEc0K4Ny 6qRVuJG+WWScY4gm8qdY= X-Received: by 2002:a1f:284a:: with SMTP id o71mr19021076vko.18.1592923908939; Tue, 23 Jun 2020 07:51:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJytlTMKnvf9B8Ug4iUoT8dtchlDL1nh4FnUKLyyI2rMRTdqy+Qi9BRrdzszyYVUuRBe4t5FZkI0S7NB7Uu6ryY= X-Received: by 2002:a1f:284a:: with SMTP id o71mr19021042vko.18.1592923908653; Tue, 23 Jun 2020 07:51:48 -0700 (PDT) MIME-Version: 1.0 References: <20200604151324.50704-1-david.coyle@intel.com> <20200623101423.9215-1-david.coyle@intel.com> In-Reply-To: <20200623101423.9215-1-david.coyle@intel.com> From: David Marchand Date: Tue, 23 Jun 2020 16:51:37 +0200 Message-ID: To: David Coyle Cc: Akhil Goyal , Declan Doherty , Pablo de Lara , "Trahe, Fiona" , Fan Zhang , "Ananyev, Konstantin" , dev , Thomas Monjalon , "Yigit, Ferruh" , brendan.ryan@intel.com, Hemant Agrawal , Anoob Joseph , "Ruifeng Wang (Arm Technology China)" , Liron Himi , Nagadheeraj Rottela , Srikanth Jampala , Gagandeep Singh , Jay Zhou , Ravi Kumar , Bruce Richardson , Olivier Matz , Honnappa Nagarahalli , Stephen Hemminger , alexr@mellanox.com, Jerin Jacob Kollanukkaran X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v2 0/6] add support for DOCSIS protocol 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" On Tue, Jun 23, 2020 at 12:36 PM David Coyle wrote: > A number of approaches to combine DOCSIS Crypto and CRC functions have > been discussed in the DPDK community to date, namely: > 1) adding a new rte_accelerator API, to provide a generic interface for > combining operations of different types > 2) using rawdev through a multi-function interface, again to provide a > generic interface for combining operations of different types > 3) adding support for DOCSIS Crypto-CRC to rte_security > > The third option above is the preferred approach for the following > reasons: > - it addresses the immediate use case to add DOCSIS Crypto-CRC support to > DPDK so that it can be consumed easily by cable equipment vendors > - it uses an already existing framework in DPDK > - it will mean much less code churn in DOCSIS applications, which already > use rte_cryptodev for encryption/decryption I guess https://patchwork.dpdk.org/project/dpdk/list/?series=9304 can be marked Superseded then. Thanks. -- David Marchand