DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Griffin, John" <john.griffin@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Jain, Deepak K" <deepak.k.jain@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] crypto/qat: make the session struct variable in size
Date: Tue, 9 Aug 2016 13:30:15 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358907B2F0@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1470325583-38741-1-git-send-email-john.griffin@intel.com>



-----Original Message-----
From: Griffin, John 
Sent: Thursday, August 4, 2016 4:46 PM
To: dev@dpdk.org
Cc: Griffin, John <john.griffin@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
Subject: [PATCH v1] crypto/qat: make the session struct variable in size

This patch changes the qat firmware session data structure from a fixed size to a variable size which is dependent on the size of the chosen algorithm.
This reduces the amount of bytes which are transferred across PCIe and thus helps to increase qat performance when the accelerator is bound by PCIe.

Signed-off-by: John Griffin <john.griffin@intel.com>
---
v1:
* Fixed a compile issue with icc.

Acked-by: Fiona Trahe <fiona.trahe@intel.com>

  reply	other threads:[~2016-08-09 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  8:30 [dpdk-dev] [PATCH] qat: change the session structure to be variable sized John Griffin
2016-08-04 10:49 ` John Griffin
2016-08-04 15:46 ` [dpdk-dev] [PATCH v1] crypto/qat: make the session struct variable in size John Griffin
2016-08-09 13:30   ` Trahe, Fiona [this message]
2016-08-30 20:53     ` De Lara Guarch, Pablo

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=348A99DA5F5B7549AA880327E580B4358907B2F0@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.griffin@intel.com \
    --cc=pablo.de.lara.guarch@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).