Re: [dpdk-dev] [PATCH] eal: make rte_lcore_cpuset and rte_lcore_to_cpu_id stable
From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2021-09-01 17:16:17
quoted
/** - * @warning - * @b EXPERIMENTAL: this API may change without prior notice. - * * Return the cpuset for a given lcore. * @param lcore_id * the targeted lcore, which MUST be between 0 and RTE_MAX_LCORE-1. * @return * The cpuset of that lcore */ -__rte_experimental rte_cpuset_t rte_lcore_cpuset(unsigned int lcore_id);I'm wondering why negative lcore_id is supported above with special meaning, but not supported here.
The DPDK API stability in this case means staying bug-for-bug compatible. I.e passing -1 as unsigned int results in UINT_MAX which is invalid.