From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>,
david.marchand@redhat.com, aman.deep.singh@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v3] app/testpmd: fix lcore ID restriction
Date: Wed, 12 Jun 2024 00:37:39 +0100 [thread overview]
Message-ID: <8c1f820e-75a6-4975-bf85-0c766287ce9d@amd.com> (raw)
In-Reply-To: <20240606112746.2643600-1-sivaprasad.tummala@amd.com>
On 6/6/2024 12:27 PM, Sivaprasad Tummala wrote:
> With modern CPUs, it is possible to have higher
> CPU count thus we can have higher RTE_MAX_LCORES.
> In testpmd application, the current config forwarding
> cores option "--nb-cores" is hard limited to 255.
>
> The patch fixes this constraint and also adjusts the lcore
> data structure to 32-bit to align with rte lcore APIs.
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2024-06-11 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:46 [PATCH] " Sivaprasad Tummala
2024-04-15 21:54 ` Stephen Hemminger
2024-04-15 21:56 ` Stephen Hemminger
2024-04-16 9:55 ` [PATCH v2] " Sivaprasad Tummala
2024-04-19 8:24 ` Ferruh Yigit
2024-04-19 11:30 ` Ferruh Yigit
2024-06-06 9:56 ` Tummala, Sivaprasad
2024-06-13 16:51 ` Ferruh Yigit
2024-06-13 19:13 ` Stephen Hemminger
2024-06-14 9:01 ` Ferruh Yigit
2024-06-14 15:27 ` Stephen Hemminger
2024-06-14 15:39 ` Ferruh Yigit
2024-06-14 17:50 ` Morten Brørup
2024-06-14 18:11 ` Stephen Hemminger
2024-06-06 11:27 ` [PATCH v3] " Sivaprasad Tummala
2024-06-11 23:37 ` Ferruh Yigit [this message]
2024-06-13 16:36 ` Ferruh Yigit
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=8c1f820e-75a6-4975-bf85-0c766287ce9d@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=sivaprasad.tummala@amd.com \
--cc=stable@dpdk.org \
/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).