DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: David Coyle <david.coyle@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
	"kevin.osullivan@intel.com" <kevin.osullivan@intel.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: RE: [EXT] [PATCH v2 0/2] crypto/scheduler: add support for security protocols
Date: Fri, 11 Aug 2023 11:09:08 +0000	[thread overview]
Message-ID: <PH0PR18MB46727FBD0837DC67BCDD03D3DF10A@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230811102401.12552-1-david.coyle@intel.com>

Hi David,

While it is desirable to add security under crypto/scheduler, would it be functionally possible if the PMDs perform stateful processing? For example, with lookaside protocol mode of IPsec, fields such as seq no & AR defines how the crypto operation can be performed. Without two PMDs sharing this (actively), how can the load balancing happen?

Said that, I agree utility of scheduler for stateless operations. My understanding is, PDCP offload that is available today is not stateful and that can leverage this. I'm not sure of DOCSIS and MACsec.

Should we make it such that only specific security sessions would be eligible for scheduler operation?

Thanks,
Anoob

> -----Original Message-----
> From: David Coyle <david.coyle@intel.com>
> Sent: Friday, August 11, 2023 3:54 PM
> To: dev@dpdk.org
> Cc: kai.ji@intel.com; kevin.osullivan@intel.com; David Coyle
> <david.coyle@intel.com>
> Subject: [EXT] [PATCH v2 0/2] crypto/scheduler: add support for security
> protocols
> 
> External Email
> 
> ----------------------------------------------------------------------
> This patchset adds support to the cryptodev scheduler PMD and unit tests
> for the existing security protocols in the security library, namely IPSec,
> MACSec, PDCP and DOCSIS.
> 
> v2:
> * Improve inclusion of rte_security header files
> * Fix typo in commit message
> 
> David Coyle (2):
>   crypto/scheduler: support security protocols
>   test/crypto: add security tests for cryptodev scheduler
> 
>  app/test/test_cryptodev.c                     |  14 +-
>  doc/guides/rel_notes/release_23_11.rst        |   3 +
>  drivers/crypto/scheduler/meson.build          |   2 +-
>  .../scheduler/rte_cryptodev_scheduler.c       | 229 ++++++++++-
>  drivers/crypto/scheduler/scheduler_failover.c |  12 +-
>  .../crypto/scheduler/scheduler_multicore.c    |  10 +-
>  .../scheduler/scheduler_pkt_size_distr.c      |  54 +--
>  drivers/crypto/scheduler/scheduler_pmd.c      |  33 ++
>  drivers/crypto/scheduler/scheduler_pmd_ops.c  | 375 +++++++++++++-----
> .../crypto/scheduler/scheduler_pmd_private.h  | 148 ++++---
>  .../crypto/scheduler/scheduler_roundrobin.c   |   6 +-
>  11 files changed, 656 insertions(+), 230 deletions(-)
> 
> --
> 2.25.1


  parent reply	other threads:[~2023-08-11 11:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 10:14 [PATCH " David Coyle
2023-08-09 10:14 ` [PATCH 1/2] crypto/scheduler: support " David Coyle
2023-08-09 10:14 ` [PATCH 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 10:23 ` [PATCH v2 0/2] crypto/scheduler: add support for security protocols David Coyle
2023-08-11 10:24   ` [PATCH v2 1/2] crypto/scheduler: support " David Coyle
2023-08-11 10:24   ` [PATCH v2 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 11:09   ` Anoob Joseph [this message]
2023-09-11 16:02     ` [EXT] [PATCH v2 0/2] crypto/scheduler: add support for security protocols Coyle, David
2023-09-13  7:02       ` Anoob Joseph
2023-09-14 15:22   ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol David Coyle
2023-09-14 15:22     ` [PATCH v3 1/2] crypto/scheduler: support " David Coyle
2023-09-18 11:02       ` [EXT] " Anoob Joseph
2023-09-19 14:16         ` Coyle, David
2023-09-14 15:22     ` [PATCH v3 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-15 10:18     ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol Power, Ciara
2023-09-15 14:02     ` Power, Ciara
2023-09-19 14:14     ` [PATCH v4 " David Coyle
2023-09-19 14:14       ` [PATCH v4 1/2] crypto/scheduler: support " David Coyle
2023-09-19 14:14       ` [PATCH v4 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-20  5:45       ` [EXT] [PATCH v4 0/2] crypto/scheduler: add support for DOCSIS security protocol Anoob Joseph
2023-09-21  7:18         ` Akhil Goyal

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=PH0PR18MB46727FBD0837DC67BCDD03D3DF10A@PH0PR18MB4672.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=david.coyle@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=kevin.osullivan@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).