From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, fiona.trahe@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature
Date: Fri, 31 Jan 2020 08:28:47 +0100 [thread overview]
Message-ID: <20200131072848.6748-1-arkadiuszx.kusztal@intel.com> (raw)
This commit fixes missing release notes for dual thread feature.
Fixes: 026f21c0b951 ("common/qat: support dual threads for enqueue/dequeue")
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
doc/guides/rel_notes/release_20_02.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/release_20_02.rst b/doc/guides/rel_notes/release_20_02.rst
index 661969c..b45d9a5 100644
--- a/doc/guides/rel_notes/release_20_02.rst
+++ b/doc/guides/rel_notes/release_20_02.rst
@@ -166,6 +166,13 @@ New Features
armv8 crypto library is not used anymore. Library name is changed
from armv8_crypto to AArch64crypto.
+* **Queue-pairs are now thread-safe on Intel QuickAssist Technology (QAT) PMD.**
+
+ Queue-pairs are thread-safe on Intel CPUs but Queues are not (that is, within
+ a single queue-pair all enqueues to the TX queue must be done from one thread and all
+ dequeues from the RX queue must be done from one thread, but enqueues and dequeues
+ may be done in different threads.).
+
Removed Items
-------------
--
2.1.0
next reply other threads:[~2020-01-31 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 7:28 Arek Kusztal [this message]
2020-01-31 7:28 ` [dpdk-dev] [PATCH] crypto/qat: fix not included release note for coalescing feature Arek Kusztal
2020-02-10 10:17 ` Trahe, Fiona
2020-02-10 10:15 ` [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature Trahe, Fiona
2020-02-12 13:17 ` 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=20200131072848.6748-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).