From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F3D844237C; Wed, 11 Jan 2023 16:14:32 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9DD0040E25; Wed, 11 Jan 2023 16:14:32 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id BAAD640A7D for ; Wed, 11 Jan 2023 16:14:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673450070; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=holYormK5e1R6BL2U+d3Vp1HBKCkAKN6+Z6CDJuury4=; b=MILK+7JTv4RKQR+6jyRiikVqBoDRTJxdPyK76Gps1JUylL7r1I2GPf01NWt0hCBho+QdSG 4S96lnY0/C1pJueU+p7PL9q3XBff1cEwimpZ0KfbRuAojJ0bP1DKgAGyqKdrYmT+/djJOh LC8GZ23cpAJbRuuaxdp1b12cbuH2ZM0= Received: from mail-pl1-f199.google.com (mail-pl1-f199.google.com [209.85.214.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-664-ornZ6cq5O1OnhLWAQD5FyA-1; Wed, 11 Jan 2023 10:14:28 -0500 X-MC-Unique: ornZ6cq5O1OnhLWAQD5FyA-1 Received: by mail-pl1-f199.google.com with SMTP id z10-20020a170902ccca00b001898329db72so10824451ple.21 for ; Wed, 11 Jan 2023 07:14:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=holYormK5e1R6BL2U+d3Vp1HBKCkAKN6+Z6CDJuury4=; b=cuJr0t5iMVgZoufH1lh/hFsii9M43WAPWIvW9eujjjkTgCNDWX370qx2FelDkovAv5 MlG+U0JDb/JuOjbGsInmrtb+vs6rzHXZ9DIpGPAywFvLE4grQftbdx+/dG9fx8bo1ZH+ c1/KDP8NojMEnMOvCqP1XrHqaxRqxhoifEvuNsYv2tZbZzgdjnn1F9x0h9HwBLrFx8du Q3h8/hACn477OBEENPUuEbWrtyY93QZeAOTj+Nk4PnaX1HKV14BhVaTeDaQEGGyEgV53 Kzf1bJ0GjOK/qJhw+2bJXRyduFRf8DqshXnEGb+NiZGSbY/DBPPsSNsXLV3PNceo7Rws s8Gg== X-Gm-Message-State: AFqh2kpGcOxtJQxi+cZ/hBuFQY2nNHjEBoukUmtl1IbEsayIPunwtk3Q uNceOSBQIj7Ad3kTa+Y7uvsC7gvBQTbdEdzAosBkXCL+ASx+0BPiWcZnH0bcXoTE1viohh96mRJ zC8Aez8porvXOiG6HSm4= X-Received: by 2002:aa7:9584:0:b0:582:46a4:87dc with SMTP id z4-20020aa79584000000b0058246a487dcmr3259110pfj.2.1673450067621; Wed, 11 Jan 2023 07:14:27 -0800 (PST) X-Google-Smtp-Source: AMrXdXulJZUcQJZZsTzsqOR7AOx058bhEUW2Y0UUj+yiM6GNYgnqD5GU2Zxtkx+CsvzDyR4guoZkMco8gD2AGTZm+FE= X-Received: by 2002:aa7:9584:0:b0:582:46a4:87dc with SMTP id z4-20020aa79584000000b0058246a487dcmr3259105pfj.2.1673450066996; Wed, 11 Jan 2023 07:14:26 -0800 (PST) MIME-Version: 1.0 References: <20220909150411.3702860-1-david.marchand@redhat.com> <20221004095132.198777-1-david.marchand@redhat.com> <1ec3f0fc-631f-2aa6-70f7-7f9b96caa2a2@amd.com> In-Reply-To: From: David Marchand Date: Wed, 11 Jan 2023 16:14:15 +0100 Message-ID: Subject: Re: [PATCH v2 0/4] crypto/ccp cleanup To: "Uttarwar, Sunil Prakashrao" Cc: "Yigit, Ferruh" , Akhil Goyal , "Namburu, Chandu-babu" , "Sebastian, Selwin" , dev , Thomas Monjalon X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Nov 18, 2022 at 12:58 PM Uttarwar, Sunil Prakashrao wrote: > Hi David, > > Please find the below update > > - only one DPDK application can use ccp crypto engines (PCI bus allow/blo= cklist is not respected, right?), > Yes, only one crypto device can be used in a DPDK application for the cry= pto operations. This is introduced from the patch crypto/ccp: convert drive= r from vdev to PCI. This is implemented as per community suggestion. Community suggested to have this driver a standard PCI driver, not a vdev o= ne. I don't remember anything about the limitation. Can you point at the discussion that leaded to this? > > - since only one crypto device is exposed, there is no way for the applic= ation to dedicate/decide how to distribute crypto operations over the diffe= rent ccp crypto engines available on the system. > > When there is no ccp device passed from the application dpdk-test-crypto-= perf, it tries to probe all CCP devices present on a system and only one de= vice can be used. It seems this is bug in the patch implemented for crypto/= ccp: convert driver from vdev to PCI and we are looking into this. Indeed. So how should we proceed? Patches 1 to 3 are ready and can be merged. I don't mind dropping patch 4 if you have a better solution/alternative. --=20 David Marchand