From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20088.outbound.protection.outlook.com [40.107.2.88]) by dpdk.org (Postfix) with ESMTP id E4548CF3 for ; Mon, 23 Apr 2018 08:39:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Owo20xPkeIz8d3N8noFmgHzqy3XxXCpqfifJWqPst8o=; b=Y72uICmwGQ2nvxU6QSloS1sYriKCjnORx78mi4+F6oF2vAo1Q7xAxOpbqlaAeuaR08ggbZpUlJEK+5JDgWk5Ebc58XdOZe8bWvXEUJzjUMP7poMMD/D+DWomdQcVbmsjcw+/gZ3r3Zejgq35EKClmEXyHW6ADN64Bam691oaVzM= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=akhil.goyal@nxp.com; Received: from [10.232.134.49] (14.142.187.166) by VI1PR04MB1392.eurprd04.prod.outlook.com (2a01:111:e400:5348::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.696.15; Mon, 23 Apr 2018 06:39:41 +0000 To: Jerin Jacob References: <1522824999-61614-1-git-send-email-abhinandan.gujjar@intel.com> <5ea61576-9124-266a-00e6-cb9f22a37f59@nxp.com> <5612CB344B05EE4F95FC5B729939F780706E5DA8@PGSMSX102.gar.corp.intel.com> <37505d55-bdc3-78fb-009b-b38ba1cdbe66@nxp.com> <20180420131438.GA15553@jerin> Cc: "Gujjar, Abhinandan S" , "hemant.agrawal@nxp.com" , "dev@dpdk.org" , "De Lara Guarch, Pablo" , "Doherty, Declan" , "Vangati, Narender" , "Rao, Nikhil" , "Eads, Gage" From: Akhil Goyal Organization: NXP Message-ID: <83734a69-619f-25e3-dc09-06844c67c8e4@nxp.com> Date: Mon, 23 Apr 2018 12:09:25 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20180420131438.GA15553@jerin> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [14.142.187.166] X-ClientProxiedBy: MA1PR0101CA0037.INDPRD01.PROD.OUTLOOK.COM (2603:1096:a00:22::23) To VI1PR04MB1392.eurprd04.prod.outlook.com (2a01:111:e400:5348::23) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-HT: Tenant X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(7168020)(4627221)(201703031133081)(201702281549075)(5600026)(48565401081)(2017052603328)(7153060)(7193020); SRVR:VI1PR04MB1392; X-Microsoft-Exchange-Diagnostics: 1; VI1PR04MB1392; 3:qlyGVvgdyTMjQSDDEJgqX+sQpfDqksZsHd9Jei1JfU0GYHq0XUVmfYvTFEC03WG/QZOKgDYFLB1hlNbQ0N/cMeFZw+K0U1jOnuaPV3PzShTAAoTFTlJDRVJ/fbHtucivjlFElO0IJRAfMfgeLbwfXBx5qV/iYIuqcoYAjL9G094I532Eq8OplGHG28xKCe4GgjUAKzWsUCjSJDpKBg80h8vv6TQyvYnE8BsPDyrQwdkWcj411LrSVlYxOmalxbx4; 25:m4B1Cqt3/LKBVBGdy9fv30ROyGA+0LdyfiLJQ+Ab4qMQgNccwAavHKtFTP22vMn368n8oB6xmMyo2Xft3lMsVt1UruyRv4oIU3aMFqH+jVj7XZ88LPmdTQGNLGjyPAfAXBqD3T7ONLIZz1OSkZefYk66t13Ybz4FfVaOkkr7EsNYtsi2zlFAYtQVa7LkDO0wI7qZCF1hX16WrYOlxbCEEsV6ThClECf1FlRFvDOz04Ow4alp3sAIx3Q26Z84maYSOfTEHhB8jy6gMh4eb+uVKzbbnvRAsf3pDrWYhSsj+aYN8vJy7Aa/1l35UuIe25pBN9j02A3xQADQo2SNPFcioA==; 31:O3N/GPDOe6xfrmXGNVuLdedWSuUP/IFV78xOD8mnz1QOXXscPhaxhddLVIN4AYykJqka/M3IrfRx9Mgtb2c9F4iy1nKeOpeR23uaUdUtT5QpdY3LQ0NrBEXjPYhb06vIKayfylKLmmdkdgaZJGqbQr5zSr7POQonRMPmQPcLo1hDimcK8XLtZUFg1mpLvKlO6s/iiBtax/tj0z/YOhgCKTuSHsDd3hPJnvYx+d2oVTA= X-MS-TrafficTypeDiagnostic: VI1PR04MB1392: X-Microsoft-Exchange-Diagnostics: 1; VI1PR04MB1392; 20:bY1xm5gf5IChZ1Rabvl8r8RDBQ5V2yOpzH+nlhiwVBVEH1peJf8tH3Hezynw4XdJAaaXGaazM8UzD0HwpmhRDexCrtsKo73a7mbSG5m2mEgMtA/E96/GBcULW5hC3PZLWz6eIVWNuZyY31/AKL4p2HzMtPcGwmHroELzFw6XEAJqXaK2b12C+G3KrQjGgiBY26j89XMDbE0jSC3XnqvBhQSAgEPFXbMYicrfOnUft+S0ZZWQd19dKVxk68lL0fDrlUzLs6S5LpYkw2yATaiWNcEiAzhO+rNJjIsmQhm8qEOGxsYh73mpNFK3BwZgi7vHZCmIqNLlEAV7lq42PyzCZPA/8mqhvJiqYWMLqImvAhcZDbxHfk+JWcjeTZQqxmmcApWv5Zp44pWWiGtgzLc6IvG6MuwpWnImbWjiQY+4zzvrTqvmuZRWtg0bVLp1LqwyqBydZw4wN0wnqrJhFL9wxnUiiVFXf3L9IOiqE+fPNYRHZqDmFgy0pHsgJZ1nz+Vx; 4:sn3JpKxD6MVFPafsCugYbWPCeEx3C+l9vRY4fNYFssN33Gr0xUyQr/OU9G2MbpykO9kMMhHbyAhHudMGEHNNNO0EeJiKihzlDSbJ5Y81uqyKDGFLkNV/OfrR3kBcNHS8C2KSvnhdKvO9otIgAqj2MTEllcjMuXEUNW5wpiT5voXj1Z3PyFqUvo3IM24+4h8DeORDGz0CwosLYtkCYgPKxaqPHP+i8czaMILyn0hczlNLIhpoPV9EIcDRae1+zDzF3AK8vIMYCzKokdF/vWBCdp18kSnM2qzWYOV0q/mYe5KosAe4D7nlqd5RXW3aoPUJeqjv7y8pYYtKJZnrewiiK48uuaX6tgEy4thAQIdKyiw= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(185117386973197)(228905959029699); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231232)(944501410)(52105095)(93006095)(93001095)(3002001)(6055026)(6041310)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011); SRVR:VI1PR04MB1392; BCL:0; PCL:0; RULEID:; SRVR:VI1PR04MB1392; X-Forefront-PRVS: 06515DA04B X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(366004)(396003)(39860400002)(376002)(346002)(39380400002)(13464003)(65806001)(53936002)(6916009)(53376002)(6246003)(186003)(6306002)(31696002)(4326008)(476003)(16526019)(86362001)(2906002)(93886005)(44832011)(2616005)(966005)(956004)(11346002)(36916002)(55236004)(36756003)(6486002)(230700001)(6666003)(446003)(305945005)(8676002)(8936002)(81166006)(65826007)(76176011)(53546011)(52116002)(5660300001)(386003)(229853002)(3846002)(6116002)(50466002)(5009440100003)(478600001)(67846002)(65956001)(66066001)(25786009)(7736002)(3260700006)(54906003)(16576012)(31686004)(23746002)(26005)(64126003)(5890100001)(47776003)(77096007)(58126008)(316002)(110426005); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR04MB1392; H:[10.232.134.49]; FPR:; SPF:None; LANG:en; MLV:nov; PTR:InfoNoRecords; Received-SPF: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; VI1PR04MB1392; 23:Gy5zW5X2Pvx7wx6UyuOCMejydjpWQ3u1oik2i?= =?Windows-1252?Q?GskGDg2Sm91FE0OSxSwgwr7KOfzExPJ05h9B9gN5p1TSKUEjiVpT5qBE?= =?Windows-1252?Q?HhDvohSQe2jgAZL4q6o0BnRFFZ6ZuolxOqJWMb9Xx+9SXUiAmniIMWkF?= =?Windows-1252?Q?qvIkeEFDAd8yIaP7VIhjRibT8FnIljEqlg8Rx0hvXwWvwoHuyhGz1apv?= =?Windows-1252?Q?UG2VmPpPFypFB9HselldKfFlI1QvmgSFnG67zXUQCMqk56IJT+12mgMf?= =?Windows-1252?Q?MAnWncDY9O68SlVAg6pRUn0hV+v1skQExFubrTfB1+nKvX9ELMfxzSXr?= =?Windows-1252?Q?gD9wyJrk/UBcaErFeh6a8GN97cyEc7Uu07VztrHsvbqk/UFyzf7hFrxw?= =?Windows-1252?Q?gtNwVAAzXmiVz2u64n0gOS3dfYNfvAcY4y5bFqHd8pvcd7bi2OXmVO0w?= =?Windows-1252?Q?lTRMHOrT2vuxBoi0cS5kdtzaro905vF65M3PkW4jbllcBsbN4EsYMiVA?= =?Windows-1252?Q?Y3QMdL8qZXjHMOPyHAYxE023LZTHj3SMqOYajZuLY6uxUF4mj7ggQMHM?= =?Windows-1252?Q?Eu1epuSLxWX6yEes8paSPOKgvbnSLMMty5W6PJPUbjDzjwJWaH+udDgj?= =?Windows-1252?Q?u9SggDM4S7SZcoW38lfNnPApllqvczTwL2uY0iRm7S0Y9+Xm6MYOmsHz?= =?Windows-1252?Q?fzw0zSIwiBDAhW06jXZ+9TXOCux1abvDKhkJMMSXVmCpaeIBTnVAoVW6?= =?Windows-1252?Q?X46QazLR/XdjyJateBL1GIpF3fSrjkMC+zsY05su0AM1S4pBc5QSZuJ0?= =?Windows-1252?Q?4B7CyrdIFajH95onZ7TWiWFKSR5WdjCs/3NrqJMEnphSws03Cno33nkd?= =?Windows-1252?Q?I30pmWqMg1gXvAdMIONDfJz4GHjtxHn+PVnZScetnWEivyNVeNEXbqIS?= =?Windows-1252?Q?BVlWi3ygqJ9wt+OIrwWd3k6pju3gUh0oWFoicSUmUonMI3oQ0+0E2w2a?= =?Windows-1252?Q?WVC38MjPtaA3wDXZ2KKy8UV64wYIeVR7D20iAfBJY20erViH04zzV0pK?= =?Windows-1252?Q?/2aoGiaC6zxNOsV9z4iCyIeMZkQ9VvwmBizP9e8qR2Z5nN7zVY0Ubp/q?= =?Windows-1252?Q?bBS+qEJHBGG4C+Ejg596HGC/yhVFR1W7wnihSMGbEOOo1Oiu7bMzbE/s?= =?Windows-1252?Q?jvuUBF3JY2bux3f8FIi3HVFQvkfU0CbT47m44u4stOX6AqF7G3Xw6xcj?= =?Windows-1252?Q?u65+djXgYTRMgqCgnDLU97OM7/sr1K/bDPCOk2/5T0wETL6RYa8KjNCT?= =?Windows-1252?Q?0nF4om/VLfmDQs/mHRYAaJlfdQ6txclURnwFHo5hZbpQlueWR6x7oI8T?= =?Windows-1252?Q?QS9xZcdLJp/y0yah07wa9WK8W22aN9X6QshFFhC8P3iycFGajkJcsLTD?= =?Windows-1252?Q?YaZoKJ9CUEpPl6yLL7Pvj2LQV2cM3cF9FwAqLeDhT+yfPbYr8mprigL1?= =?Windows-1252?Q?i5cX8E1weUzIKUJiylGJ4C7o8lPo7p/zYwCm2xLro6PpzDlHwDFaMYDN?= =?Windows-1252?Q?AzLxhISKc+ctgrKq9kiVii90778fJR9VHKSE9zkneWKPAExZ46t+bY8j?= =?Windows-1252?Q?9ITYmQAGoLvgpmU7wrgTHZs+UKILI1IXA/el6KLTq0X?= X-Microsoft-Antispam-Message-Info: NoGmK+3/8bpUfYCJlRyw4CFjSY/NLFYBHRB4g9hdXTDTCmVBfRUi8dj7J1chIDDZtYAx8Xl/rjIE8jzS40wV6ZdHrfhc5YDuItQ8LkbjsVO4Ksek9C+ipvPRpiu3Lm+7v/jbPZmbkievG9AjDla9x91Gp1xzvhlcQYupoLbuD5cLD5SoCcDUP2i44apX7vtZ X-Microsoft-Exchange-Diagnostics: 1; VI1PR04MB1392; 6:Zky9Ek2CLQwnlrsI9dzLuRgCwXB6g4vn6MvmFDiJ1D3eqs5KA0umRSxuFp9g+2RDdDakcLVcN0ipMUprqCuANba6M/L/XRBziW11kkgDHewwEbuSvWgQjRqFzFC3XCSYAmLQ68EkPXGoRH79PdDC6aKuOF4+0LDQsUBKAqd4QBh9TVBNYADEtLY9zUiwZTZ+tqmiRmlUWGK3wMJEeAGVliXkk1S2VtqhbCdP8KqJ7DGpq4WowDy/ike1Q6S6ydkUYtAtE0Qp9vtkLAnDnWlHPzvebYvz3k7pfWBc9dAOiq8CdDWHfozQeqFfK8yVkHVtTh4YDNNx3W7d6/lJ8Pq3tjugtZnPAJ9oK6rebdRUJY7QTqhKxTZdj+yLdHkwmyVCtoME1hsfwM4ZkKci1NiLlLUirJ8y3jbF6ikw9diXBVXWslmGVMWnMZfz2aXtuUW2pE+DO50wrsNMYi5XLh/jRA==; 5:2RKSjg19C2t8b89FhTRyZ41HpQ+naeSLCb5lZL5x4F36mfouUwH+9pg5xsUrSaeFoiTpwmZMHHqepYCrd7t3ia9RzK2PhUO1KmV4yPRvR9JjZ7UjPxOjMA7GDQCUuuziUC4N1I7cNWuUdhof8YqwxQmYij8CwNZgTRmIZZY9hcI=; 24:4Sjsklmtw1DPiQoHK1o0MeHvtjWM2XGO92XfjMSnKfFgxuj19539enIGyUco47lV4nodumZrjDMSbJILT4RYo4ndbq6wPftQ8dAVd57MiEI= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; VI1PR04MB1392; 7:pjcSTpVh5sVTVI3HR11NGu7fl88fHJZK0JYIY6spmHd+2OoV8zs7HR2YAUWLU/pYChgpVuLrfHRNAEEYkXrwVkd67T21c7gp3sRpuJ4HsBTU+mglV6rBARmyPWWNTvKeoBKiqTHyUTNmgaV0zyc2VAqB9py1wPsuMujD+8Gqqb62Pe9tgZXlcUowhnnE0EH91fRX2IHChoNiFzLu6kuOQtqwGRJsdsKhWE3H3xxPpIcYfo3oNGGnnBcSiZ3Diq1q X-MS-Office365-Filtering-Correlation-Id: 7db064ff-9ef8-4824-cbe4-08d5a8e4ffca X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Apr 2018 06:39:41.8720 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 7db064ff-9ef8-4824-cbe4-08d5a8e4ffca X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR04MB1392 Subject: Re: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation 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: Mon, 23 Apr 2018 06:39:46 -0000 On 4/20/2018 6:44 PM, Jerin Jacob wrote: > -----Original Message----- >> Date: Fri, 20 Apr 2018 17:04:36 +0530 >> From: Akhil Goyal >> To: "Gujjar, Abhinandan S" , >> "jerin.jacob@caviumnetworks.com" , >> "hemant.agrawal@nxp.com" , "dev@dpdk.org" >> >> CC: "De Lara Guarch, Pablo" , "Doherty, >> Declan" , "Vangati, Narender" >> , "Rao, Nikhil" , "Eads, >> Gage" >> Subject: Re: [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation >> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 >> Thunderbird/45.8.0 >> >> Hi Abhinandan/ Jerin, >> On 4/18/2018 11:51 AM, Gujjar, Abhinandan S wrote: >>> Hi Akhil, >>> >>> Please find the comments inline. >>> >>>> -----Original Message----- >>>> From: Akhil Goyal [mailto:akhil.goyal@nxp.com] >>>> Sent: Tuesday, April 17, 2018 7:48 PM >>>> To: Gujjar, Abhinandan S ; >>>> jerin.jacob@caviumnetworks.com; hemant.agrawal@nxp.com; dev@dpdk.org >>>> Cc: De Lara Guarch, Pablo ; Doherty, Declan >>>> ; Vangati, Narender >>>> ; Rao, Nikhil ; Eads, Gage >>>> >>>> Subject: Re: [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation >>>> >>>> Hi Abhinandan, >>>> >>>> I have not reviewed the patch completely. But I have below query for further >>>> review. >>>> On 4/4/2018 12:26 PM, Abhinandan Gujjar wrote: >>>>> Signed-off-by: Abhinandan Gujjar >>>>> Signed-off-by: Nikhil Rao >>>>> Signed-off-by: Gage Eads >>>>> --- >>>> >>>> [..snip..] >>>>> + >>>>> +int __rte_experimental >>>>> +rte_event_crypto_adapter_queue_pair_add(uint8_t id, >>>>> + uint8_t cdev_id, >>>>> + int32_t queue_pair_id) >>>>> +{ >>>>> + struct rte_event_crypto_adapter *adapter; >>>>> + struct rte_eventdev *dev; >>>>> + struct crypto_device_info *dev_info; >>>>> + uint32_t cap; >>>>> + int ret; >>>>> + >>>>> + RTE_EVENT_CRYPTO_ADAPTER_ID_VALID_OR_ERR_RET(id, -EINVAL); >>>>> + >>>>> + if (!rte_cryptodev_pmd_is_valid_dev(cdev_id)) { >>>>> + RTE_EDEV_LOG_ERR("Invalid dev_id=%" PRIu8, cdev_id); >>>>> + return -EINVAL; >>>>> + } >>>>> + >>>>> + adapter = eca_id_to_adapter(id); >>>>> + if (adapter == NULL) >>>>> + return -EINVAL; >>>>> + >>>>> + dev = &rte_eventdevs[adapter->eventdev_id]; >>>>> + ret = rte_event_crypto_adapter_caps_get(adapter->eventdev_id, >>>>> + cdev_id, >>>>> + &cap); >>>>> + if (ret) { >>>>> + RTE_EDEV_LOG_ERR("Failed to get adapter caps dev %" PRIu8 >>>>> + "cdev %" PRIu8, id, cdev_id); >>>>> + return ret; >>>>> + } >>>>> + >>>>> + dev_info = &adapter->cdevs[cdev_id]; >>>>> + >>>>> + if (queue_pair_id != -1 && >>>>> + (uint16_t)queue_pair_id >= dev_info->dev->data->nb_queue_pairs) { >>>>> + RTE_EDEV_LOG_ERR("Invalid queue_pair_id %" PRIu16, >>>>> + (uint16_t)queue_pair_id); >>>>> + return -EINVAL; >>>>> + } >>>>> + >>>>> + if (cap & RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT) { >>>>> + RTE_FUNC_PTR_OR_ERR_RET( >>>>> + *dev->dev_ops->crypto_adapter_queue_pair_add, >>>>> + -ENOTSUP); >>>>> + if (dev_info->qpairs == NULL) { >>>>> + dev_info->qpairs = >>>>> + rte_zmalloc_socket(adapter->mem_name, >>>>> + dev_info->dev->data->nb_queue_pairs >>>> * >>>>> + sizeof(struct crypto_queue_pair_info), >>>>> + 0, adapter->socket_id); >>>>> + if (dev_info->qpairs == NULL) >>>>> + return -ENOMEM; >>>>> + } >>>>> + >>>>> + ret = (*dev->dev_ops->crypto_adapter_queue_pair_add)(dev, >>>>> + dev_info->dev, >>>>> + queue_pair_id); >>>> >>>> crypto_adapter_queue_pair_add is supposed to attach a queue >>>> (queue_pair_id) of cryptodev(dev_info->dev) to event device (dev). >>>> But how will the underlying implementation attach it to event device without >>>> knowing the eventdev queue_id. This information was coming in the RFC >>>> patches with the parameter (rte_event_crypto_queue_pair_conf). >>>> Why is this removed and if removed how will the driver attach the queue. >>>> I can see that rte_event is passed in the session private data but how can we >>>> attach the crypto queue with event dev queue? >>> >>> Yes, this was present in the first version of the RFC which is similar to eth rx adapter. >>> After couple of discussions, thread http://dpdk.org/dev/patchwork/patch/31752/), >>> it was changed. In eth rx adapter, eth queues are mapped to eventdev, whereas in crypto >>> adapter the sessions are mapped to eventdev. Since event info is present along with the >>> session, the get API has to be called in respective API to get the event information and >>> then map to eventdev. >>> >> >> I think the intent of that discussion was misunderstood from our end. >> But this is not going to work for hardware devices. >> >> Because in case of hardware implementation, the scheduling is done in >> hardware and hardware cannot call the get API to get the event information >> then map to event device. Actually the scheduling has happened before the >> crypto_op is dequeued from the event port. So there is no point of set/get >> private data in our case. >> >> We need to map the crypto queues to the event queue_ids at the time of >> queue_pair add API. In hardware scheduler, we map n(may be 1-8) crypto >> queues to m event queues(<= n). We can assign multiple sessions to any >> crypto queue pair, and after the crypto op is received by event queue, they >> are appropriately scheduled by hardware to event ports. >> >> Session based mapping to event queue cannot be supported. Our design is same >> as that of eth rx adapter. > > Crypto queue pair to eventdev queue mapping should be supported. But > That's a limited set. meaning if an application needs millions of IPSec SA sessions > then we can not map it. So, IMO, If an HW/SW can not support session > based mapping then it needs to be exposed/abstracted through capabilities. > > crypto qp to event queue mapping will be supported in all adapter > implementation. > > Does that sounds OK? > Yes, that will be fine for us. Thanks, Akhil