From: Akhil Goyal <gakhil@marvell.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>,
<hemant.agrawal@nxp.com>, <anoobj@marvell.com>,
<pablo.de.lara.guarch@intel.com>, <fiona.trahe@intel.com>,
<declan.doherty@intel.com>, <matan@nvidia.com>, <g.singh@nxp.com>,
<fanzhang.oss@gmail.com>, <jianjay.zhou@huawei.com>,
<asomalap@amd.com>, <ruifeng.wang@arm.com>,
<konstantin.v.ananyev@yandex.ru>, <radu.nicolau@intel.com>,
<ajit.khaparde@broadcom.com>, <rnagadheeraj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: [PATCH v2 0/2] cryptodev: add queue pair priority
Date: Tue, 24 Sep 2024 22:07:59 +0530 [thread overview]
Message-ID: <20240924163801.1841582-1-gakhil@marvell.com> (raw)
In-Reply-To: <20240731115445.1771803-1-gakhil@marvell.com>
Changes in v2:
- added release notes and removed deprecation notice.
- removed gerrit-id
Akhil Goyal (2):
cryptodev: add queue pair priority
app/crypto-perf: test queue pair priority
app/test-crypto-perf/cperf_options.h | 3 +++
app/test-crypto-perf/cperf_options_parsing.c | 20 ++++++++++++++++++
app/test-crypto-perf/main.c | 6 +++++-
doc/guides/rel_notes/deprecation.rst | 3 ---
doc/guides/rel_notes/release_24_11.rst | 3 +++
doc/guides/tools/cryptoperf.rst | 5 +++++
lib/cryptodev/rte_cryptodev.h | 22 ++++++++++++++++++++
7 files changed, 58 insertions(+), 4 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2024-09-24 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 11:54 [PATCH 1/2] " Akhil Goyal
2024-07-31 11:54 ` [PATCH 2/2] app/crypto-perf: test " Akhil Goyal
2024-09-24 16:37 ` Akhil Goyal [this message]
2024-09-24 16:38 ` [PATCH v2 1/2] cryptodev: add " Akhil Goyal
2024-09-24 16:38 ` [PATCH v2 2/2] app/crypto-perf: test " Akhil Goyal
2024-10-09 14:03 ` [PATCH v2 0/2] cryptodev: add " 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=20240924163801.1841582-1-gakhil@marvell.com \
--to=gakhil@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=asomalap@amd.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianjay.zhou@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=matan@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=rnagadheeraj@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).