[dpdk-dev] [PATCH] crypto: remove unused digest-appended feature

2016-11-30 Thread De Lara Guarch, Pablo
> -Original Message- > From: Griffin, John > Sent: Friday, November 18, 2016 6:16 PM > To: Trahe, Fiona; dev at dpdk.org > Cc: De Lara Guarch, Pablo; Jastrzebski, MichalX K; Kusztal, ArkadiuszX > Subject: Re: [PATCH] crypto: remove unused digest-appended feature > > On 17/11/16 17:33,

[dpdk-dev] [PATCH] crypto: remove unused digest-appended feature

2016-11-18 Thread John Griffin
On 17/11/16 17:33, Fiona Trahe wrote: > The cryptodev API had specified that if the digest address field was > left empty on an authentication operation, then the PMD would assume > the digest was appended to the source or destination data. > This case was not handled at all by most PMDs and

[dpdk-dev] [PATCH] crypto: remove unused digest-appended feature

2016-11-17 Thread Fiona Trahe
The cryptodev API had specified that if the digest address field was left empty on an authentication operation, then the PMD would assume the digest was appended to the source or destination data. This case was not handled at all by most PMDs and incorrectly handled by the QAT PMD. As no bugs were

[dpdk-dev] [PATCH] crypto: remove unused digest-appended feature

2016-11-17 Thread Fiona Trahe
The cryptodev API had specified that if the digest address field was left empty on an authentication operation, then the PMD would assume the digest was appended to the source or destination data. This case was not handled at all by most PMDs and incorrectly handled by the QAT PMD. As no bugs were