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 2685245D6B; Thu, 21 Nov 2024 19:02:53 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E746C40A81; Thu, 21 Nov 2024 19:02:52 +0100 (CET) Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by mails.dpdk.org (Postfix) with ESMTP id 890AF40A6B; Thu, 21 Nov 2024 19:02:51 +0100 (CET) Received: from pps.filterd (m0431384.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 4ALH8cUF024626; Thu, 21 Nov 2024 10:02:50 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h= cc:content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to; s=pfpt0220; bh=5ydxkYWaz+kcLNOgufeYaVI ltHtQydPzTEkU0rGsCjM=; b=ezu1vNCvv0WOSXO5oAV+jln/UPsz5NhtW8TZhRv tqVLV/3CWGaZM2QZmb91rQoOeoPor8KwniOyq+JtdtC8Z2ZqMZNDgewtTEgKpP5H nUmtDV9ehkQdN4HEUqLt1U7KGlan5JY2l+sXmhZxOrRyZbJ3yyqy7wagxCgAYu+x H5yvuccS9a2F+3UySG3fEDoO70jeJneAP26L7fWdJr/I/n4xluXKDWcwsbMVXTo8 CdhPQqaVAMgHYK/sbmiJgWqAZVvZa0hhpVzS+U2FNODHiFmMzNOhvCm7ldT/8Usg aMTIEdTzLM+liQiwfyS7u14FqNSMuqenG7DEPnnVkNg1+6g== Received: from dc6wp-exch02.marvell.com ([4.21.29.225]) by mx0a-0016f401.pphosted.com (PPS) with ESMTPS id 43290n03q5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Nov 2024 10:02:50 -0800 (PST) Received: from DC6WP-EXCH02.marvell.com (10.76.176.209) by DC6WP-EXCH02.marvell.com (10.76.176.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.4; Thu, 21 Nov 2024 10:02:48 -0800 Received: from maili.marvell.com (10.69.176.80) by DC6WP-EXCH02.marvell.com (10.76.176.209) with Microsoft SMTP Server id 15.2.1544.4 via Frontend Transport; Thu, 21 Nov 2024 10:02:48 -0800 Received: from IN-lckQE5Rwctls.marvell.com (IN-lckQE5Rwctls.marvell.com [10.28.163.68]) by maili.marvell.com (Postfix) with ESMTP id AB1AC3F7075; Thu, 21 Nov 2024 10:02:45 -0800 (PST) From: Gowrishankar Muthukrishnan To: , Maxime Coquelin , Chenbo Xia , Jay Zhou CC: , Anoob Joseph , Akhil Goyal , Jerin Jacob , Fan Zhang , Gowrishankar Muthukrishnan Subject: [RFC] crypto/virtio: add vhost-vdpa backend Date: Thu, 21 Nov 2024 23:32:16 +0530 Message-ID: <20241121180219.1234-1-gmuthukrishn@marvell.com> X-Mailer: git-send-email 2.37.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-ORIG-GUID: PFf8YEztBRghAoZqHko_bK3hKNBeF23F X-Proofpoint-GUID: PFf8YEztBRghAoZqHko_bK3hKNBeF23F X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.687,Hydra:6.0.235,FMLib:17.0.607.475 definitions=2020-10-13_15,2020-10-13_02,2020-04-07_01 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 Hi, We are adding support for vDPA user backend for virtio-crypto PMD in DPDK. We have come up with functional changes which is similar to the support available in net: commit 6b901437056eed3ed7c9932c333ba24ac5be116f net/virtio: introduce vhost-vDPA backend vhost-vDPA is a new virtio backend type introduced by vDPA kernel framework, which provides abstraction to the vDPA devices and exposes an unified control interface through a char dev. Our current development reuses some code from net/virtio/virtio_user/, and we realize that we could keep a few things in common between net and crypto, such as: -> vhost_vdpa.c (and its header file) from net/virtio/virtio_user/: Except for VHOST_VDPA_GET_DEVICE_ID and enabling queue pairs, virtio_user_backend_ops can be reused. -> virtio_user_dev.c (and its header file) from net/virtio/virtio_user/: virtio_user_dev_init and its capabilities differ. -> virtio_cvq.c (and its header file) from net/virtio/: There is a difference in the usage of the first and last descriptors for the virtio header and status (net vs. crypto). We need to standardize these codes to ensure they work universally. Therefore, we propose creating a driver/common/virtio/ directory to house them. This approach will help address common issues and extend Virtio functionalities shared between crypto and net. For example, the crypto PMD can benefit from packed ring support. We welcome your valuable feedback and any suggestions. Thanks, Gowrishankar -- 2.37.1