DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pankaj Joshi <pankaj.joshi63@gmail.com>
To: qat-linux <qat-linux@intel.com>, dev@dpdk.org
Subject: [dpdk-dev] Getting corrupted ESP packet
Date: Tue, 4 Oct 2016 21:33:44 +0530	[thread overview]
Message-ID: <CAOYs48EWTcFhv8zCvxQkQJFw9-4RRf9dDm3vmZ_Mdt7dFfWWzg@mail.gmail.com> (raw)

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 16:03 UTC|newest]

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

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=CAOYs48EWTcFhv8zCvxQkQJFw9-4RRf9dDm3vmZ_Mdt7dFfWWzg@mail.gmail.com \
    --to=pankaj.joshi63@gmail.com \
    --cc=dev@dpdk.org \
    --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).