From: Stephen Hemminger <stephen@networkplumber.org>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: <david.marchand@redhat.com>, <aman.deep.singh@intel.com>,
<yuying.zhang@intel.com>, <ferruh.yigit@amd.com>, <dev@dpdk.org>,
<stable@dpdk.org>
Subject: Re: [PATCH] app/testpmd: fix lcore ID restriction
Date: Mon, 15 Apr 2024 14:56:50 -0700 [thread overview]
Message-ID: <20240415145650.00a5969a@hermes.local> (raw)
In-Reply-To: <20240415194631.124343-1-sivaprasad.tummala@amd.com>
On Mon, 15 Apr 2024 19:46:31 +0000
Sivaprasad Tummala <sivaprasad.tummala@amd.com> wrote:
> --- a/app/test-pmd/testpmd.h
> +++ b/app/test-pmd/testpmd.h
> @@ -84,7 +84,7 @@ extern volatile uint8_t f_quit;
> /* Maximum number of pools supported per Rx queue */
> #define MAX_MEMPOOL 8
>
> -typedef uint8_t lcoreid_t;
> +typedef uint32_t lcoreid_t;
> typedef uint16_t portid_t;
> typedef uint16_t queueid_t;
> typedef uint16_t streamid_t;
> --
The other DPDK API's are using unsigned for lcore_id.
On the platforms that DPDK supports both are the same size.
next prev parent reply other threads:[~2024-04-15 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:46 [PATCH] app/testpmd: fix lcore ID restriction Sivaprasad Tummala
2024-04-15 21:54 ` Stephen Hemminger
2024-04-15 21:56 ` Stephen Hemminger [this message]
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
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=20240415145650.00a5969a@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=sivaprasad.tummala@amd.com \
--cc=stable@dpdk.org \
--cc=yuying.zhang@intel.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 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.