From: Stephen Hemminger <stephen@networkplumber.org>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, lijuan.tu@intel.com, juraj.linkes@pantheon.tech,
ohilyard@iol.unh.edu, david.marchand@redhat.com,
thomas@monjalon.net, jerinj@marvell.com,
bruce.richardson@intel.com, kathleen.capella@arm.com, nd@arm.com,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [PATCH v2 2/2] examples/l3fwd: make RX and TX queue size configurable
Date: Thu, 10 Feb 2022 16:53:41 -0800 [thread overview]
Message-ID: <20220210165341.348c5708@hermes.local> (raw)
In-Reply-To: <20220211002607.80058-2-honnappa.nagarahalli@arm.com>
On Fri, 11 Feb 2022 00:26:07 +0000
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> wrote:
> diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
> index acd186ab7d..afe94cd1d7 100644
> --- a/examples/l3fwd/main.c
> +++ b/examples/l3fwd/main.c
> @@ -341,6 +341,8 @@ print_usage(const char *prgname)
> " [-P]"
> " [--lookup]"
> " --config (port,queue,lcore)[,(port,queue,lcore)]"
> + " [--rx-queue-size]"
> + " [--tx-queue-size]"
Shouldn't there be a NPKTS after the arg?
" [--rx-queue-size NPKTS]"
next prev parent reply other threads:[~2022-02-11 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 6:04 [PATCH 1/2] examples/l3fwd: use single set of variables throughout the code Honnappa Nagarahalli
2022-02-02 6:04 ` [PATCH 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-08 7:41 ` Ruifeng Wang
2022-02-02 8:49 ` [PATCH 1/2] examples/l3fwd: use single set of variables throughout the code Bruce Richardson
2022-02-11 0:26 ` [PATCH v2 " Honnappa Nagarahalli
2022-02-11 0:26 ` [PATCH v2 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-11 0:53 ` Stephen Hemminger [this message]
2022-02-11 3:43 ` Honnappa Nagarahalli
2022-02-11 1:01 ` Stephen Hemminger
2022-02-11 3:38 ` Honnappa Nagarahalli
2022-02-23 6:09 ` [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout the code Honnappa Nagarahalli
2022-02-23 6:09 ` [PATCH v3 2/2] examples/l3fwd: make RX and TX queue size configurable Honnappa Nagarahalli
2022-02-23 6:13 ` [PATCH v3 1/2] examples/l3fwd: use single set of variables throughout the code Honnappa Nagarahalli
2022-02-23 9:22 ` Kevin Traynor
2022-03-01 1:56 ` Han, YingyaX
2022-03-08 9:22 ` 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=20220210165341.348c5708@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
--cc=kathleen.capella@arm.com \
--cc=lijuan.tu@intel.com \
--cc=nd@arm.com \
--cc=ohilyard@iol.unh.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.