From: Sudheendra Sampath <giveback4fun@gmail.com>
To: "Varghese, Vipin" <Vipin.Varghese@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
Cc: "konstantin.ananyev@huawei.com" <konstantin.ananyev@huawei.com>,
"wathsala.vithanage@arm.com" <wathsala.vithanage@arm.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"viktorin@cesnet.cz" <viktorin@cesnet.cz>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>
Subject: Re: [PATCH v5 v5 2/3] app: add topology aware test case
Date: Thu, 16 Apr 2026 22:19:12 -0700 [thread overview]
Message-ID: <c0451147f1b2b7ba217c8e770e806e4a45f3e374.camel@gmail.com> (raw)
In-Reply-To: <PH7PR12MB859698AFEFF656FD908A729882202@PH7PR12MB8596.namprd12.prod.outlook.com>
Hi Vipin,
Pardon my ignorance. I am not sure I understand what you mean by
"current function test format".
Can you let me know where I can read about the current function test
format ?
Thanks
Sudheendra Sampath
next prev parent reply other threads:[~2026-04-17 5:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241105102849.1947-1-vipin.varghese@amd.com>
2025-02-13 3:09 ` [PATCH v4 0/4] Introduce Topology NUMA grouping for lcores Varghese, Vipin
2025-02-13 8:34 ` Thomas Monjalon
2025-02-13 9:18 ` Morten Brørup
2025-03-03 9:06 ` Varghese, Vipin
2025-03-04 10:08 ` Morten Brørup
2025-03-05 7:43 ` Mattias Rönnblom
2025-03-03 8:59 ` Varghese, Vipin
2025-03-17 13:46 ` Jan Viktorin
2025-04-09 10:08 ` Varghese, Vipin
2025-06-03 6:03 ` Varghese, Vipin
2026-01-17 18:57 ` Stephen Hemminger
2026-01-19 14:55 ` [PATCH v4 0/4] Introduce Topology NUMA grouping for cores Varghese, Vipin
2026-04-14 19:38 ` [PATCH v5 0/3] eal/topology: introduce topology-aware lcore grouping Vipin Varghese
2026-04-14 19:38 ` [PATCH v5 v5 1/3] eal/topology: add Topology grouping for lcores Vipin Varghese
2026-04-15 14:06 ` Morten Brørup
2026-04-15 17:52 ` Varghese, Vipin
2026-04-14 19:38 ` [PATCH v5 v5 2/3] app: add topology aware test case Vipin Varghese
2026-04-15 5:21 ` Sudheendra Sampath
2026-04-16 7:22 ` Varghese, Vipin
2026-04-16 13:19 ` Varghese, Vipin
2026-04-17 1:21 ` Varghese, Vipin
2026-04-17 5:19 ` Sudheendra Sampath [this message]
2026-04-17 9:55 ` Varghese, Vipin
2026-04-14 19:38 ` [PATCH v5 v5 3/3] doc: add new section topology Vipin Varghese
2026-04-14 20:22 ` [PATCH v5 0/3] eal/topology: introduce topology-aware lcore grouping Stephen Hemminger
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=c0451147f1b2b7ba217c8e770e806e4a45f3e374.camel@gmail.com \
--to=giveback4fun@gmail.com \
--cc=Sivaprasad.Tummala@amd.com \
--cc=Vipin.Varghese@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=viktorin@cesnet.cz \
--cc=wathsala.vithanage@arm.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