From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 3/3] crypto/qat: enable TX tail writes coalescing
Date: Fri, 15 Sep 2017 13:17:37 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589294A3B@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <8aada4555a65d6ceb8b581f7909020a487ee9f3b.1505142402.git.anatoly.burakov@intel.com>
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Tuesday, September 12, 2017 10:31 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; Griffin, John <john.griffin@intel.com>; Jain, Deepak K
> <deepak.k.jain@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH v2 3/3] crypto/qat: enable TX tail writes coalescing
>
> Don't write CSR tail until we processed enough TX descriptors.
>
> To avoid crypto operations sitting in the TX ring indefinitely,
> the "force write" threshold is used:
> - on TX, no tail write coalescing will occur if number of inflights
> is below force write threshold
> - on RX, check if we have a number of crypto ops enqueued that is
> below force write threshold that are not yet submitted to
> processing.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2017-09-15 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1503651900.git.anatoly.burakov@intel.com>
2017-08-25 9:30 ` [dpdk-dev] [DPDK] [PATCH 1/3] qat: remove atomics Anatoly Burakov
2017-09-04 14:39 ` De Lara Guarch, Pablo
2017-09-12 9:31 ` [dpdk-dev] [PATCH v2 0/3] performance enhancements for QAT driver Anatoly Burakov
2017-09-12 9:31 ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: remove atomics Anatoly Burakov
2017-09-15 11:35 ` Trahe, Fiona
2017-09-12 9:31 ` [dpdk-dev] [PATCH v2 2/3] crypto/qat: enable RX head writes coalescing Anatoly Burakov
2017-09-15 11:55 ` Trahe, Fiona
2017-09-12 9:31 ` [dpdk-dev] [PATCH v2 3/3] crypto/qat: enable TX tail " Anatoly Burakov
2017-09-15 13:17 ` Trahe, Fiona [this message]
2017-09-18 11:03 ` [dpdk-dev] [PATCH v2 0/3] performance enhancements for QAT driver De Lara Guarch, Pablo
2017-08-25 9:30 ` [dpdk-dev] [DPDK] [PATCH 2/3] qat: enable RX head writes coalescing Anatoly Burakov
2017-08-25 9:30 ` [dpdk-dev] [DPDK] [PATCH 3/3] qat: enable TX tail " Anatoly Burakov
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=348A99DA5F5B7549AA880327E580B43589294A3B@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).