From: Thomas Monjalon <thomas@monjalon.net>
To: Wisam Jaddo <wisamm@mellanox.com>
Cc: jackmin@mellanox.com, david.marchand@redhat.com, dev@dpdk.org,
arybchenko@solarflare.com
Subject: Re: [dpdk-dev] [PATCH v2] app/flow-perf: fix condition of hairpin queues setup
Date: Mon, 06 Jul 2020 10:15:42 +0200 [thread overview]
Message-ID: <13068074.RF7ULXdDSz@thomas> (raw)
In-Reply-To: <20200706075318.8048-1-wisamm@mellanox.com>
06/07/2020 09:53, Wisam Jaddo:
> The hairpin queue is the one that start from normal rxq,
> and will be less than nr_queues where nr_queues is the
> sum of normal and hairpin
>
> Fixes: bf3688f1e816 ("app/flow-perf: add insertion rate calculation")
> Cc: wisamm@mellanox.com
>
> Signed-off-by: Wisam Jaddo <wisamm@mellanox.com>
> Reviewed-by: Asaf Penso <asafp@mellanox.com>
>
> ---
> v2:
> * Add documentation of hairpin peering and allocating logic.
> * Add documentation for some variables.
> ---
> --- a/app/test-flow-perf/main.c
> +++ b/app/test-flow-perf/main.c
> @@ -1012,8 +1012,26 @@ init_port(void)
> rte_strerror(-ret), port_id);
>
> if (hairpinq != 0) {
> + /* Each hairpin queue setup need a hairpin configuration
> + * object, which determine the TX path for hairpin.
> + *
> + * The peering here represent the TX side, which mean the
> + * peer.port represent TX port, and peer.queue represent
> + * tx_queue.
> + *
> + * So if RXQ=4 and TXQ=4, and first hairpin_q is 4 after
> + * [0, 1, 2, 3], then tx_queue is TXQ+i which is 4 as well.
> + *
> + * hairpinq: represent the number of hairpin queues needed
> + * to be initialized.
> + *
> + * In 0 case means no hairpin queues needed which is the
> + * default.
> + *
> + * hairpin_q: represent hairpin queue id to be initialized.
> + */
Variables doc should be on variable declaration.
next prev parent reply other threads:[~2020-07-06 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 8:10 [dpdk-dev] [PATCH] " Wisam Jaddo
2020-07-05 15:39 ` Asaf Penso
2020-07-05 20:39 ` Thomas Monjalon
2020-07-06 8:00 ` Wisam Monther
2020-07-06 7:53 ` [dpdk-dev] [PATCH v2] " Wisam Jaddo
2020-07-06 8:15 ` Thomas Monjalon [this message]
2020-07-06 8:32 ` [dpdk-dev] [PATCH v3] " Wisam Jaddo
2020-07-16 14:16 ` [dpdk-dev] [PATCH v4] " Wisam Jaddo
2020-07-19 13:11 ` 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=13068074.RF7ULXdDSz@thomas \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jackmin@mellanox.com \
--cc=wisamm@mellanox.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).