patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: <stephen@networkplumber.org>, <rkerur@gmail.com>,
	<david.marchand@redhat.com>, <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] examples/l3fwd: fix max Tx queue count
Date: Mon, 11 Jan 2021 22:48:07 +0530	[thread overview]
Message-ID: <20210111171806.GA181038@outlook.office365.com> (raw)
In-Reply-To: <20201214190255.16429-1-hkalra@marvell.com>

Ping...

On Tue, Dec 15, 2020 at 12:32:55AM +0530, Harman Kalra wrote:
> In l3fwd no of transmit queues is calculated based on no of
> lcores with which it is launched. Hence maximum no of tx
> queues possible per port should depend on RTE_MAX_LCORE value.
> 
> Fixes: 268888b5b020 ("examples/l3fwd: modularize")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
> ---
>  examples/l3fwd/main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
> index d62dec434..bb49e5faf 100644
> --- a/examples/l3fwd/main.c
> +++ b/examples/l3fwd/main.c
> @@ -48,7 +48,7 @@
>  #include "l3fwd.h"
>  #include "l3fwd_event.h"
>  
> -#define MAX_TX_QUEUE_PER_PORT RTE_MAX_ETHPORTS
> +#define MAX_TX_QUEUE_PER_PORT RTE_MAX_LCORE
>  #define MAX_RX_QUEUE_PER_PORT 128
>  
>  #define MAX_LCORE_PARAMS 1024
> -- 
> 2.18.0
> 

  reply	other threads:[~2021-01-11 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 19:02 Harman Kalra
2021-01-11 17:18 ` Harman Kalra [this message]
2021-01-12  8:58 ` David Marchand
2021-01-12 18:18   ` [dpdk-stable] [EXT] " Harman Kalra
2021-01-12 18:24   ` [dpdk-stable] [PATCH v2] examples/l3fwd: remove limitation on " Harman Kalra
2021-01-19 12:16     ` David Marchand

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=20210111171806.GA181038@outlook.office365.com \
    --to=hkalra@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=rkerur@gmail.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).