DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Luse, Paul E" <paul.e.luse@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Question on AESNI PMD
Date: Fri, 9 Mar 2018 22:04:27 +0000	[thread overview]
Message-ID: <82C9F782B054C94B9FC04A331649C77AA6ABA230@fmsmsx104.amr.corp.intel.com> (raw)

Hi,

I'm working on an SPDK module that uses the DPDK cryptodev framework, initially I'm using the AESNI PMD and have a few questions. in the doc it says that only in-place is supported however I see code in set_mb_job_params() just after the comment "Mutable crypto operation parameters" it appears to support a separate src and dst m_buf so curious about that.

For my use case (storage) I'm using external data buffers so I can't use that code anyways but I was able to make some minor changes and am able to pass in different src and dst m_bufs that point to my own data buffers (not in the packet) and it seems to be working fine.

So my 2 questions are:

(1) is the documented in-place limitation simply not correct?

(2) would there be any upstream interest in supporting a patch that enables m_bufs using external data buffers for src and dst?

Thanks!
Paul

             reply	other threads:[~2018-03-09 22:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 22:04 Luse, Paul E [this message]
2018-03-09 22:08 Luse, Paul E
2018-03-09 22:35 ` Thomas Monjalon
2018-03-13 14:16   ` Luse, Paul E
2018-03-13 19:18     ` De Lara Guarch, Pablo
2018-03-13 19:28       ` Luse, Paul E
2018-03-15  0:43         ` Luse, Paul E
2018-03-20 14:33           ` Luse, Paul E

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=82C9F782B054C94B9FC04A331649C77AA6ABA230@fmsmsx104.amr.corp.intel.com \
    --to=paul.e.luse@intel.com \
    --cc=dev@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).