From: Akhil Goyal <gakhil@marvell.com>
To: Srujana Challa <schalla@marvell.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Srujana Challa <schalla@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples/ipsec-secgw: add support for event vector
Date: Sun, 31 Oct 2021 13:22:04 +0000 [thread overview]
Message-ID: <CO6PR18MB448433D0E15D7FFDA7B240B9D8899@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210914131424.1298729-1-schalla@marvell.com>
Hi Konstantin/Radu,
> Adds event vector support to inline protocol offload mode.
> By default vector support is disabled, it can be enabled by
> using the option --event-vector.
> Additional options to configure vector size and vector timeout are
> also implemented and can be used by specifying --vector-size and
> --vector-tmo.
>
> Signed-off-by: Srujana Challa <schalla@marvell.com>
> ---
> Depends-on: series-18262 ("security: Improve inline fast path routines")
> Depends-on: series-18322 ("eventdev: simplify Rx adapter event vector
> config")
>
> v2:
> * Set rte_event_vector::attr_valid if all packets in the vector uses
> same port.
Any comments on this patch. It has been in patchworks from quite some time.
Regards,
Akhil
next prev parent reply other threads:[~2021-10-31 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 10:03 [dpdk-dev] [PATCH] " Srujana Challa
2021-09-14 13:14 ` [dpdk-dev] [PATCH v2] " Srujana Challa
2021-10-31 13:22 ` Akhil Goyal [this message]
2021-11-01 10:39 ` Ananyev, Konstantin
2021-11-01 14:03 ` Nicolau, Radu
2021-11-03 3:24 ` [dpdk-dev] [PATCH v3] " Nithin Dabilpuram
2021-11-03 16:07 ` 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=CO6PR18MB448433D0E15D7FFDA7B240B9D8899@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=schalla@marvell.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).