Hi Akhil, > -----Original Message----- > From: Akhil Goyal <gak...@marvell.com> > Sent: Wednesday, July 27, 2022 5:26 AM > To: Ji, Kai <kai...@intel.com>; dev@dpdk.org > Cc: Anoob Joseph <ano...@marvell.com>; hemant.agra...@nxp.com; > Zhang, Roy Fan <roy.fan.zh...@intel.com>; Chandubabu Namburu > <cha...@amd.com>; Ruifeng Wang <ruifeng.w...@arm.com>; > ajit.khapa...@broadcom.com; Michael Shamis <michae...@marvell.com>; > Nagadheeraj Rottela <rnagadhee...@marvell.com>; ma...@nvidia.com; Jay > Zhou <jianjay.z...@huawei.com> > Subject: RE: [EXT] [dpdk-dev v1] lib/cryptodev: multi-process IPC request > handler > > This is a library change you should cc all PMD owners while sending patch. Kai is in holiday at the moment and will be back in a week. I will sync with him then. > > > This patch add in multi-process IPC request handler function in rte > > cryptodev. This function intend to support a queue-pair configuration > > request to allow the secondary process to reconfigure the queue-pair > > setup'ed by the primary process. > > Who will release the queue pair already setup by primary in the first place?
Fan: If the queue pair already setup by primary the secondary shall not recreate it but use it instead. > Currently, all queues are setup by primary and secondary uses them. > So if a queue is re-initialized by secondary, and if it is being used in > primary > process, > Wont that drop packets abruptly if the queue is re-initialized? You are right. What about creating a variable in the queue pair with either PID or thread id who own the queue pair? > > Also, I see register API but not deregister. There will be V2 for that. Regards, Fan
