> -----Original Message----- > From: dev [mailto:[email protected]] On Behalf Of Declan Doherty > Sent: Wednesday, July 19, 2017 3:03 PM > To: Rybalchenko, Kirill <[email protected]>; Zhang, Roy Fan > <[email protected]> > Cc: [email protected] > Subject: Re: [dpdk-dev] [PATCH v1] crypto/scheduler: fix multicore > scheduler reordering > > On 18/07/2017 11:35 AM, Kirill Rybalchenko wrote: > > Operations can be dequeued from the reordering ring only after they > > were dequeued from the crypto pmd with > rte_cryptodev_dequeue_burst() > > function. It is not correct to dequeue them when status just changed > > from RTE_CRYPTO_OP_STATUS_NOT_PROCESSED to any other value, as > the > > operations still can be processed by crypto pmd internally. > > Now multicore scheduler workers mark status of all dequeued from > > crypto pmd operations with CRYPTO_OP_STATUS_BIT_COMPLETE bit set. > > Scheduler will dequeue crypto operations from reordering ring only > > when this status bit is set. Prior to put this operation to output > > buffer, scheduler clears this bit, so the application gets unmodified > > status from crypto pmd. > > > > Fixes: 4c07e0552f0a ("crypto/scheduler: add multicore scheduling > > mode") > > > > Signed-off-by: Kirill Rybalchenko <[email protected]> > > --- > ... > > > Acked-by: Declan Doherty <[email protected]>
Applied to dpdk-next-crypto. Thanks, Pablo
