From: <akhil.goyal@nxp.com>
To: <declan.doherty@intel.com>, <fiona.trahe@intel.com>,
<pablo.de.lara.guarch@intel.com>
Cc: <thomas.monjalon@6wind.com>, <dev@dpdk.org>,
<hemant.agrawal@nxp.com>, <deepak.k.jain@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: [dpdk-dev] [PATCH] doc: add deprecation note to add parameter in rte_cryptodev_info.sym
Date: Tue, 14 Feb 2017 17:41:14 +0530 [thread overview]
Message-ID: <20170214121114.10590-1-akhil.goyal@nxp.com> (raw)
From: Akhil Goyal <akhil.goyal@nxp.com>
A new parameter is planned to be added in 17.05 release in
rte_cryptodev_info.sym - max_nb_sessions_per_qp.
This will allow applications to know the maximum number of session
which can be attached to queue_pairs of device.
Signed-off-by: Akhil Goyal <akhil.goyal@nxp.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 97d87fd..487f798 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -56,3 +56,8 @@ Deprecation Notices
to specify which type of instance to create (single or burst), and
additional calls for ``rte_distributor_poll_pkt_burst`` and
``rte_distributor_return_pkt_burst``, among others.
+
+* cryptodev: A new parameter ``max_nb_sessions_per_qp`` will be added to
+ ``rte_cryptodev_info.sym``. Some drivers may support limited number of
+ sessions per queue_pair. With this new parameter application will know
+ how many sessions can be mapped to each queue_pair of a device.
--
2.9.3
next reply other threads:[~2017-02-14 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 12:11 akhil.goyal [this message]
2017-02-14 10:34 ` Doherty, Declan
2017-02-14 10:49 ` Trahe, Fiona
2017-02-14 11:19 ` De Lara Guarch, Pablo
2017-02-14 20:43 ` 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=20170214121114.10590-1-akhil.goyal@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.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).