DPDK usage discussions
 help / color / mirror / Atom feed
From: Meng Wang <meng.w.wang@oracle.com>
To: users@dpdk.org
Subject: [dpdk-users] [crypto-QAT] how does qat sym pmd setup session
Date: Thu, 23 May 2019 14:49:39 -0400	[thread overview]
Message-ID: <afe1766a-cdc6-9300-1d53-fb8ad93c21a2@oracle.com> (raw)

Hi,

I find it a bit confusing that in qat_sym_pmd.c, session_pool was not 
set when sym qp was setup, as shown below.

static int qat_sym_qp_setup(struct rte_cryptodev *dev, uint16_t qp_id,
     const struct rte_cryptodev_qp_conf *qp_conf,
     int socket_id, struct rte_mempool *session_pool __rte_unused)

However, later on when qat sym builds request it explicitly looks for 
session info in qat_sym_build_request(), which ends up with failure.

Did I miss something during device and qp setup? How does qat sym setup 
session info for qp?

Thanks,
Meng

             reply	other threads:[~2019-05-23 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 18:49 Meng Wang [this message]
2019-05-24  9:37 ` 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=afe1766a-cdc6-9300-1d53-fb8ad93c21a2@oracle.com \
    --to=meng.w.wang@oracle.com \
    --cc=users@dpdk.org \
    /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).