From: Akhil Goyal <gakhil@marvell.com>
To: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Srujana Challa <schalla@marvell.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: RE: [PATCH] doc: announce change to cryptodev cb function prototype
Date: Tue, 12 Jul 2022 11:55:59 +0000 [thread overview]
Message-ID: <CO6PR18MB448430BDB8A36738A18445ABD8869@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220624134524.3461406-1-schalla@marvell.com>
Hi Hemant,
Can you please ack this deprecation notice?
> Subject: [PATCH] doc: announce change to cryptodev cb function prototype
>
> Function rte_cryptodev_cb_fn prototype will be extended to
> add new parameter qp_id, to return queue pair ID, which got
> error interrupt to the application, so that application can
> reset that particular queue pair.
>
> https://mails.dpdk.org/archives/dev/2022-June/245428.html
>
> Signed-off-by: Srujana Challa <schalla@marvell.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..d6c94f8ac8 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -112,6 +112,11 @@ Deprecation Notices
> session and the private data of session. An opaque pointer can be exposed
> directly to application which can be attached to the ``rte_crypto_op``.
>
> +* cryptodev: The function pointer ``rte_cryptodev_cb_fn`` will be updated to
> + have another parameter ``qp_id`` to return the queue_pair ID which got error
> + interrupt to the application so that application can reset that particular
> + queue pair.
> +
> * security: Hide structure ``rte_security_session`` and expose an opaque
> pointer for the private data to the application which can be attached
> to the packet while enqueuing.
> --
> 2.25.1
next prev parent reply other threads:[~2022-07-12 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:45 Srujana Challa
2022-06-24 18:09 ` Akhil Goyal
2022-07-12 11:57 ` Hemant Agrawal
2022-07-06 9:11 ` Zhang, Roy Fan
2022-07-11 14:52 ` Jerin Jacob
2022-07-12 11:55 ` Akhil Goyal [this message]
2022-07-17 10:37 ` Thomas Monjalon
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=CO6PR18MB448430BDB8A36738A18445ABD8869@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=roy.fan.zhang@intel.com \
--cc=schalla@marvell.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).