DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Pankaj Joshi <pankaj.joshi63@gmail.com>,
	qat-linux <qat-linux@intel.com>,  "dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] Getting corrupted ESP packet
Date: Tue, 4 Oct 2016 18:15:01 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435890ED3D7@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <CAOYs48EWTcFhv8zCvxQkQJFw9-4RRf9dDm3vmZ_Mdt7dFfWWzg@mail.gmail.com>

Hi Pankaj,

I can't think of any way the QAT PMD could return a larger packet than it's been sent, can you provide some more details of your use-case please, e.g. which cipher algorithm, which auth algorithm are you using?
Are you using out-of-place or in-place? i.e. are the m_src and m_dst mbuf pointers in the rte_crypto_sym_op the same or different?
Can you try doing the same operation using the AESNI_MB PMD?

Regards,
Fiona
 

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pankaj Joshi
> Sent: Tuesday, October 4, 2016 5:04 PM
> To: qat-linux <qat-linux@intel.com>; dev@dpdk.org
> Subject: [dpdk-dev] Getting corrupted ESP packet
> 
> Hello All,
> 
> I am using QAT library for data encryption ( for coletocreek card).
> I am sending 98 byte ICMP data to the hardware, at successful time it is
> returning 166 byte of data as ESP packet.
> But sometimes it is returning through callback function 180 byte of data ,
> which is corrupted one .
> Can anyone tell, how I can resolve this issue and why it is happening when
> I am sending same data to the hardware.

> 
> Regards,
> Pankaj Joshi

      reply	other threads:[~2016-10-04 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 16:03 Pankaj Joshi
2016-10-04 18:15 ` Trahe, Fiona [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=348A99DA5F5B7549AA880327E580B435890ED3D7@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.griffin@intel.com \
    --cc=pankaj.joshi63@gmail.com \
    --cc=qat-linux@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).