From: Wisam Monther <wisamm@nvidia.com>
To: "psatheesh@marvell.com" <psatheesh@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] app/flow-perf: added option to support flow priority
Date: Sun, 7 Nov 2021 09:26:06 +0000 [thread overview]
Message-ID: <DM4PR12MB50393BB3B58A09F043D2473EA4909@DM4PR12MB5039.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211102105042.2207792-1-psatheesh@marvell.com>
Hi,
> -----Original Message-----
> From: psatheesh@marvell.com <psatheesh@marvell.com>
> Sent: Tuesday, November 2, 2021 12:51 PM
> To: Wisam Monther <wisamm@nvidia.com>
> Cc: dev@dpdk.org; Satheesh Paul <psatheesh@marvell.com>
> Subject: [dpdk-dev] [PATCH v3] app/flow-perf: added option to support flow
> priority
>
> From: Satheesh Paul <psatheesh@marvell.com>
>
> Added support to create flows with priority attribute set randomly between
> 0 and a user supplied maximum value. This is useful to measure performance
> on NICs which may have to rearrange flows to honor flow priority.
>
> Removed the lower limit of 100000 flows per batch.
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
> v3:
> * Fixed checkpatch errors
>
> v2:
> * Changed "--max-priority" to "--random-priority".
> * Added support to take seed for pseudo-random number generator.
> * Updated documentation for the above.
>
Acked-by: Wisam Jaddo <wisamm@nvidia.com>
BRs,
Wisam Jaddo
next prev parent reply other threads:[~2021-11-07 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 4:08 [dpdk-dev] [PATCH] " psatheesh
2021-11-01 9:06 ` Wisam Monther
2021-11-02 10:39 ` Satheesh Paul
2021-11-02 10:39 ` [dpdk-dev] [PATCH v2] " psatheesh
2021-11-02 10:50 ` [dpdk-dev] [PATCH v3] " psatheesh
2021-11-07 9:26 ` Wisam Monther [this message]
2021-11-08 9:32 ` 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=DM4PR12MB50393BB3B58A09F043D2473EA4909@DM4PR12MB5039.namprd12.prod.outlook.com \
--to=wisamm@nvidia.com \
--cc=dev@dpdk.org \
--cc=psatheesh@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).