From: Shijith Thotton <sthotton@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Srujana Challa <schalla@marvell.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples/l3fwd: add changes to use event vector
Date: Wed, 22 Sep 2021 15:36:52 +0000 [thread overview]
Message-ID: <PH0PR18MB4425C582A37E727245F9C4EAD9A29@PH0PR18MB4425.namprd18.prod.outlook.com> (raw)
>04/09/2021 09:46, Shijith Thotton:
>> +* ``--enable-vector:`` Optional, Enable event vectorization. Only valid if --
>mode=eventdev.
>
>As for the IPsec example, the option name --event-vector
>would be more appropriate because "vector" can refer to something else.
>
Will change option name to --event-vector.
>> +
>> +* ``--vector-size:`` Optional, Max vector size if event vectorization is enabled.
>> +
>> +* ``--vector-tmo-ns:`` Optional, Max timeout to form vector in nanoseconds if
>event vectorization is enabled.
>
>Better to have a common prefix "event" for all three options.
>
Makes sense, will change in next version.
next reply other threads:[~2021-09-22 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:36 Shijith Thotton [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-30 19:15 [dpdk-dev] [PATCH] " Shijith Thotton
2021-09-04 7:46 ` [dpdk-dev] [PATCH v2] " Shijith Thotton
2021-09-21 21:42 ` Thomas Monjalon
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=PH0PR18MB4425C582A37E727245F9C4EAD9A29@PH0PR18MB4425.namprd18.prod.outlook.com \
--to=sthotton@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=schalla@marvell.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).