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 not included release note for coalescing feature
Date: Fri, 31 Jan 2020 08:28:48 +0100 [thread overview]
Message-ID: <20200131072848.6748-2-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <20200131072848.6748-1-arkadiuszx.kusztal@intel.com>
This patch fixes not included in original patch release note
Fixes: 6cde900bd59d ("common/qat: remove tail write coalescing")
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
doc/guides/rel_notes/release_20_02.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/rel_notes/release_20_02.rst b/doc/guides/rel_notes/release_20_02.rst
index d19a7f5..661969c 100644
--- a/doc/guides/rel_notes/release_20_02.rst
+++ b/doc/guides/rel_notes/release_20_02.rst
@@ -184,6 +184,15 @@ Removed Items
the Technical Board decided to disable all the kernel modules
by default from 20.02 version.
+* **Removed coalescing feature from Intel QuickAssist Technology (QAT) PMD.**
+
+ The internal tail write coalescing feature was removed as not compatible with
+ dual-thread feature. It was replaced with a threshold feature. At busy times
+ if only a small number of packets can be enqueued, each enqueue causes
+ an expensive MMIO write. These MMIO write occurrences can be optimised by using
+ the new threshold parameter on process start. Please see qat documentation for
+ more details.
+
API Changes
-----------
--
2.1.0
next prev parent reply other threads:[~2020-01-31 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 7:28 [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature Arek Kusztal
2020-01-31 7:28 ` Arek Kusztal [this message]
2020-02-10 10:17 ` [dpdk-dev] [PATCH] crypto/qat: fix not included release note for coalescing feature 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-2-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).