From: "Doherty, Declan" <declan.doherty@intel.com>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: cryptodev API question with out of order support
Date: Mon, 20 Mar 2023 11:58:05 +0000 [thread overview]
Message-ID: <4a103137-330d-ff31-1ac4-73e8823fa8ab@intel.com> (raw)
In-Reply-To: <CO6PR12MB5396D292970A7A1578B35F31C1809@CO6PR12MB5396.namprd12.prod.outlook.com>
Hey Suanming,
I haven't been actively involved in the development of DPDK in a number
of years but as far as I'm aware (and I don't believe this has changed
recently), out of order processing from the cryptodev API user
perspective is not supported, and for most scenarios I'm aware of (for
symmetric crypto processing) it would not be desired, as data path
protocols like IPsec or TLS expect packet order to be maintained.
I know the crypto scheduler PMD allows out of order processing of
operations on worker cores, when it is working in a load balancing mode,
but it's default behaviour is to guarantee that packets/operations are
returned in order to the user after processing.
If there are use cases for out of order processing (maybe for asymmetric
crypto) then I expected that at a minimum a per queue pair setup option
would be required and possibly a completion queue mechanism might be
required.
Regards
Declan
On 20/03/2023 09:28, Suanming Mou wrote:
> Hi Declan,
>
> While reading the cryptodev API and define docs, I don’t see some places
> mention the out of order support.
>
> Does current crypto enqueue and dequeue function support out of order
> mode? Or should we add a hint capability flag for that?
>
> Not sure if such topics have been discussed before, can you please help
> to clarify?
>
> Thanks,
>
> Suanming Mou
>
next prev parent reply other threads:[~2023-03-20 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:28 Suanming Mou
2023-03-20 11:58 ` Doherty, Declan [this message]
2023-03-20 12:05 ` Suanming Mou
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=4a103137-330d-ff31-1ac4-73e8823fa8ab@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=suanmingm@nvidia.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).