Thanks for reply. BTW I guess "CONFIG_RTE_MAX_LCORE=128" means no more than 128 cores. But what does "CONFIG_RTE_MAX_LCORE_FREQS=64" mean?
On Wed, Jun 3, 2020 at 1:51 PM Vincent Li <[email protected]> wrote: > > > On Tue, 2 Jun 2020, Ding Ma wrote: > > > Really appreciate your help. Two follow-ups: > > - it actually works on 48 cores server and do you know why? (The problem > > server is 96 cores) > > I think Stephen might mean your pre-build DPDK might not be built with 32 > cores, I am not familiar with this neither, but I here is my grep search: > > /usr/src/dpdk# egrep 'CORE|CPU' x86_64-native-linux-gcc/.config > > CONFIG_RTE_MAX_LCORE=128 > # Recognize/ignore architecture we compile for. AVX/AVX512 CPU flags for > performance/power testing. > CONFIG_RTE_MAX_LCORE_FREQS=64 > CONFIG_RTE_TEST_PMD_RECORD_CORE_CYCLES=n > > I guess your pre-built DPDK might have CONFIG_RTE_MAX_LCORE built less > than 96, you can either rebuilt your DPDK RPM package or rebuild from DPDK > source with cores >= 96, say 128 > > > > - which part in config I need to change? (Sorry I am a noob) . Also, I am > > using pre-built RPM to install dpdk, do I have to rebuild the RPM on 96 > > cores server in order to run it on the 96 cores server? > > > > On Tue, Jun 2, 2020 at 7:21 PM Stephen Hemminger < > [email protected]> > > wrote: > > > > > On Tue, 2 Jun 2020 18:04:57 -0700 > > > Ding Ma <[email protected]> wrote: > > > > > > > Hope it's the right way to ask DPDK questions. I am new to DPDK > world and > > > > got an error while setting up dpdk on my server. any idea about > where I > > > > should look at? > > > > > > > > > > > > 1. Error: rte_eal port num [0] is not match the pciidlist [4] > > > > 2. EAL: Error - exiting with code: 1 > > > > 3. Cause: Generate core list error > > > > > > > > > > > > Full paste: > > > > ttps://pastebin.com/zea7514Y <https://pastebin.com/zea7514Y> > > > > > > Your DPDK is built for only 32 CPU's and you have a machine with 128. > > > Change your config and move on to the next issue. > > > > > > * There are patches in review to avoid this in future versions of DPDK. > > > > > >
